That would be great
Bruno: Fast and Git-friendly open-source API client (Postman alternative)
311–320 of 444 posts
Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)
#312It looks great. Postman always loses me because I usually only need simple requests and I have to go through a big structure. As a result, it only ever edits one request over and over again, which I have configured correctly. The key thing about Postman is that I was able to configure my own script to refresh the API token. For the internal API, we have a short-lived "access_token" token (~1 minute) and then a long-l…
$ eval $(stat -s refresh_token); #set some stat vars, will use change time st_ctime
$ if [ $(expr $(date '+%s') - $st_ctime) > 86400 ]; then rm refresh_token; fi
$ if [ ! -f refresh_token ]; then ./get_refresh_token.sh; fiRe: Bruno: Fast and Git-friendly open-source API client (Postman alternative)
#313I really like the idea of serializing requests to a Git-friendly text format. But if we want a Git-friendly text format, why not mimic HTTP/1.1 request syntax as much as possible? Maybe with Jekyll-like YAML front matter for metadata that doesn’t fit? So for Get Users.bru instead of the current example of: meta { name: Get Users type: http seq: 1 } get { url: https://reqres.in/api/users body: none } headers { Content…
Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)
#314Can someone help me understand the difference between the .bru file and an OpenAPI spec (Swagger), aren't they representing the same thing with different syntax?
Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)
#315It looks great. Postman always loses me because I usually only need simple requests and I have to go through a big structure. As a result, it only ever edits one request over and over again, which I have configured correctly. The key thing about Postman is that I was able to configure my own script to refresh the API token. For the internal API, we have a short-lived "access_token" token (~1 minute) and then a long-l…
Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)
#316This looks great, and less bloated than Postman but after a few seconds of testing the Linux (Snap) version, I noticed the system file browser opens with what is probably an invalid font (all characters appear as squares). As well, it would be nice to be able to import my rather large postman collections (an vice versa - provide a collection from Bruno to a Postman user). Looking forward to when I can switch to this…
How does the Bruno snap compare to the Postman snap, in terms of startup times? I know snaps are slow, but the Postman snap takes forever (~16 seconds)
Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)
#317Looks great! Postman dug its own grave after selling out itself for VC money. The “File over app” philosophy is a direction that we should be supporting after the Post-ZIRP VC money world. 1: https://stephango.com/file-over-app
It should also be easier to comply with GDPR’s Right to Data Portability (article 20) for applications that follow the “File over app” philosophy.
1: https://www.edpb.europa.eu/sme-data-protection-guide/respect...
Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)
#318I myself use Paw [0] because it's native to MacOS, but I'm a little bit worried for it's longevity as it being supported by a SaaS business. But so far it's been great to document API for my personal projects. [0]: https://paw.cloud/
I’m envy? I’m hoping for a native GUI application for Linux. Electron looks ugly, it doesn’t integrate, fails to handle HiDPI usually, in best case it eats a ridiculous amount of memory (factor 5x compared to native) and in worst case it has security issues due to Blink and lot of JS. Electron is Flash for the Desktop.
It is exactly the opposite of flash.
Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)
#319Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)
#320Earlier quoted context omitted.
Once CEO asked me: "why are you spending months of your valuable time to create a tool to solve a thing, instead paying $10/month?" "I know developers never pay, but why?"
It's not the money, it's the control you relinquish in the process. The potential costs of the risks involved are much, much greater than $10/month.