Insomnia REST client now requires an account • Hacker News Board

Re: Insomnia REST client now requires an account

#81

Post by helloanoop » Thu, Sep 28, 2023, 7:31 PM UTC

PH95VuimJjqBqy wrote: post #80

helloanoop wrote: post #65

Earlier quoted context omitted.

Oauth2 flow is missing (which should be released by tomorrow), Otherwise you shouldn't encounter any pain points. The app has been in development over 2 years, and community (early adopters) has been using it for over year. It's fairly stable except the occasional blip. I built the tool for myself, I wanted my collections to co-exist alongside my backend code and be able to version it via git. So I ended up creating…

I see the claim of saving everything on the filesystem and collaboration via git. - Is there a way to handle secrets outside of this flow? - Can we set/reference variables between collections? collection A sets a variable, collection B uses it. also, a small bit of feedback from someone that briefly played with Bruno this morning. - moving requests in a collection via drag/drop isn't obvious and it's actually a pain…

> I see the claim of saving everything on the filesystem and collaboration via git.

yes, ALL IN on git :) based collaboration

> Is there a way to handle secrets outside of this flow?

Check: https://docs.usebruno.com/secrets-management/overview.html Two ways of handling secrets.

> collection A sets a variable, collection B uses it.

In bruno collection is the first class citizen, environments reside inside a collection. There is plan to support global environments for the use case you mentioned.

> moving requests in a collection via drag/drop isn't obvious and it's actually a pain if you're trying to replace the top item.

yes, this ux needs to be improved and there is a bug in drag and drop which should be fixed.

Re: Insomnia REST client now requires an account

#82

Post by pleoxy » Thu, Sep 28, 2023, 7:50 PM UTC

helloanoop wrote: post #54

Try Bruno - https://github.com/usebruno/bruno - Free and Opensource IDE for exploring and testing APIs - It is lightweight with MIT license - Bruno stores your collections directly in a folder on your filesystem - Use git for collaboration - No cloud sync. Fully offline. PS: I am the creator of this project

Stop.

We don't talk about Bruno.

/S

Sorry, couldn't resist. :)

Re: Insomnia REST client now requires an account

#83

Post by out_of_protocol » Thu, Sep 28, 2023, 7:52 PM UTC

helloanoop wrote: post #54

Try Bruno - https://github.com/usebruno/bruno - Free and Opensource IDE for exploring and testing APIs - It is lightweight with MIT license - Bruno stores your collections directly in a folder on your filesystem - Use git for collaboration - No cloud sync. Fully offline. PS: I am the creator of this project

I think docs need simple list of what exactly supported (and what is not) by the Bruno. E.g. is GRPC supported?

Re: Insomnia REST client now requires an account

#84

Post by PH95VuimJjqBqy » Thu, Sep 28, 2023, 7:57 PM UTC

helloanoop wrote: post #81

PH95VuimJjqBqy wrote: post #80

Earlier quoted context omitted.

I see the claim of saving everything on the filesystem and collaboration via git. - Is there a way to handle secrets outside of this flow? - Can we set/reference variables between collections? collection A sets a variable, collection B uses it. also, a small bit of feedback from someone that briefly played with Bruno this morning. - moving requests in a collection via drag/drop isn't obvious and it's actually a pain…

> I see the claim of saving everything on the filesystem and collaboration via git. yes, ALL IN on git :) based collaboration > Is there a way to handle secrets outside of this flow? Check: https://docs.usebruno.com/secrets-management/overview.html Two ways of handling secrets. > collection A sets a variable, collection B uses it. In bruno collection is the first class citizen, environments reside inside a collection…

Excellent, thank you for the quick response.

I'm guessing your recommendation for dealing with separate environments (dev/qa/etc) would then be a single collection with folders underneath and environments defined w/i that collection.

In that sense collections for bruno seem to be more akin to "projects" and are not really equivalent to postman collections in that sense.

That's workable, it good to know the environments are collection specific rather than global.

Re: Insomnia REST client now requires an account

#85

Post by magixx » Thu, Sep 28, 2023, 8:25 PM UTC

j_crick wrote: post #79

- Market yourself up as a Postman alternative - Work for some time - Do the same shit as Postman - ... - Profit? Really? I don’t know even. Why does it have to be the same story all the time? It’s become so tiring.

Because recurring revenue vs no revenue or one time revenue is hard to pass up as a business.

I do think cloud based sharing/features do have their place in a tool like this however.

Re: Insomnia REST client now requires an account

#86

Post by stratosgear » Thu, Sep 28, 2023, 8:29 PM UTC

mfinelli wrote: post #67

ReptileMan wrote: post #63

So we are once again in the - please give alternatives. No clouds, no syncs, no other bullsit ... Postman is dead, insomnia seemed like good alternative.

A while ago I built https://github.com/mfinelli/cui because I wanted something like postman that ran in my terminal. It's a little rough around the edges but it does the job for me

I have settled for Thunderclient vscode extension. Realy nice...

Re: Insomnia REST client now requires an account

#87

Post by tomaszs » Thu, Sep 28, 2023, 8:35 PM UTC

According to the discussion and brief browsing of code changes I don't see any intention or proof it's for promoting the cloud solution. The title is not justified. The report was made 13h ago after beta versions released. There's no response yet.

update : found response here: https://github.com/Kong/insomnia/issues/6577#issuecomment-17...

I understand it's intentional

Re: Insomnia REST client now requires an account

#88

Post by helloanoop » Thu, Sep 28, 2023, 8:45 PM UTC

PH95VuimJjqBqy wrote: post #84

helloanoop wrote: post #81

Earlier quoted context omitted.

> I see the claim of saving everything on the filesystem and collaboration via git. yes, ALL IN on git :) based collaboration > Is there a way to handle secrets outside of this flow? Check: https://docs.usebruno.com/secrets-management/overview.html Two ways of handling secrets. > collection A sets a variable, collection B uses it. In bruno collection is the first class citizen, environments reside inside a collection…

Excellent, thank you for the quick response. I'm guessing your recommendation for dealing with separate environments (dev/qa/etc) would then be a single collection with folders underneath and environments defined w/i that collection. In that sense collections for bruno seem to be more akin to "projects" and are not really equivalent to postman collections in that sense. That's workable, it good to know the environmen…

Exactly!

Re: Insomnia REST client now requires an account

#89

Post by helloanoop » Thu, Sep 28, 2023, 8:48 PM UTC

pleoxy wrote: post #82

helloanoop wrote: post #54

Try Bruno - https://github.com/usebruno/bruno - Free and Opensource IDE for exploring and testing APIs - It is lightweight with MIT license - Bruno stores your collections directly in a folder on your filesystem - Use git for collaboration - No cloud sync. Fully offline. PS: I am the creator of this project

Stop. We don't talk about Bruno. /S Sorry, couldn't resist. :)

We don't talk about Bruno. no. no. no :)

We don't talk about bruno.

BTW, GRPC will be supported soon. Will create a roadmap section in the docs.

Re: Insomnia REST client now requires an account

#90

Post by PH95VuimJjqBqy » Thu, Sep 28, 2023, 9:00 PM UTC

helloanoop wrote: post #88

PH95VuimJjqBqy wrote: post #84

Earlier quoted context omitted.

Excellent, thank you for the quick response. I'm guessing your recommendation for dealing with separate environments (dev/qa/etc) would then be a single collection with folders underneath and environments defined w/i that collection. In that sense collections for bruno seem to be more akin to "projects" and are not really equivalent to postman collections in that sense. That's workable, it good to know the environmen…

Exactly!

Sorry to deluge you, I found another UI bug.

if you rename a collection with existing requests in it, the result will be two collections, 1 with the new name and 1 with the old name. The new name will have all the requests as expected.

The old name will be a "ghost" collection, you can't seem to do anything with it, including rename it again. If you close bruno and re-open, the old named collection will be gone.