Show HN: Yaade – An open-source, self-hosted, collaborative API dev environment(github.com)

100 pointsby jonrosner4 yıl önce11 comments

Show HN: Yaade – An open-source, self-hosted, collaborative API dev environment

https://github.com/EsperoTech/yaade

3 comments

Using Postman has become an essential part of my development workflow. Unfortunately I found that I was very limited by the local nature of Postman. I built Yaade to easily and securely share my API collections with my teammates. Alternatives like Hoppscotch may provide an awesome user interface but their self-hosting capabilities just lack far behind of what I need for actual production use.

Feel free to try it out and comment. Running Yaade just takes two docker commands! Your opinion is very welcome.

arcastroe4 yıl önce

This looks great! I'm a big fan of postman and bigger fan of self-hosted solutions. Can't wait to try it.

Regarding the note: > DO NO FORGET TO ADD A TRAILING SLASH TO YOUR URL https://yaade.example.com -> https://yaade.example.com/.

Would it not be possible for the chrome extension to handle this on its own?

jonrosner4 yıl önce

Thanks for your reply! Looking forward to hearing your feedback. Yes things like this will be handled by the tool in the future. For now I want to gather as much feedback as possible to know which are the most wanted features / improvements. I have a roadmap in mind already and want to confirm if that is what other users want too!

tluyben24 yıl önce

Thanks for making this. I find postman deteriorating rapidly for years in their quest to make money.

jonrosner4 yıl önce

Thanks. I feel the same way. I hate not knowing which features will be behind a paywall.

Aeolun4 yıl önce

Does this do something like Insomnia environments? I really like having only one API collection that I can use with our 15 different environments.

jonrosner4 yıl önce

thanks for your comment. Environment for collections is definitely on the roadmap. Probably one of the first things I will implement next. How would you want a feature like this to look? Is having multiple collections with the same content but different environments OK or would you rather have one collection with multiple environments and you can switch them at the click of a button?

Aeolun4 yıl önce

The second one (one collection has multiple environments). I’m thinking of a situation in which I have the same API deployed to dev/qa/production environments.

I don’t really use much more than ‘{host}/api/v1/dostuff’, but not having duplicate collections you have to make changes in is really nice.

0des4 yıl önce

The name is awkward

jonrosner4 yıl önce

Haha thanks for your comment. May I ask where you are from? I am from germany and I thought you could just pronounce it like the gem Jade.

0des4 yıl önce

Ah that makes sense. Latin america, in my head it looks like yawd like Todd, and I sat there for a bit sounding it out