Earlier quoted context omitted.
Our stack is comprised of 15 stateless micro services all built with Nodejs. MongoDB, Redis and Neo4j are used for persistence, caching, and dependency management. The fundamental piece our system is RabbitMQ which is used as our event queue. The architecture designed around events. When an application dies or a commit is made, an event propagated through the system. We also use a lot of open source software. Docker…
What is your experience with using Docker Swarm in a production environment? I have heard conflicting views regarding it.
Runnable Sandboxes: Full-stack environments for every GitHub branch
51–56 of 56 posts
Re: Runnable Sandboxes: Full-stack environments for every GitHub branch
#52Sounds a lot like Heroku review apps[1] 1: https://devcenter.heroku.com/articles/github-integration-rev...
Hey appleton - Here are some differences 1) You don't have to re-configure your environment variables and 3rd party APIs for each branch on Runnable. Every branch runs in the same sandboxed environment with the same env variables and 3rd party services. With the help of an HTTP proxy and a dynamic DNS server, we can route traffic to the right set of containers for the branch you want to test. 2) Runnable is built on…
And it's really cool that we have Heroku alternatives.
Re: Runnable Sandboxes: Full-stack environments for every GitHub branch
#53What features/problems does Runnable solve over https://elasticbox.com?
Also, who did your promo video https://www.youtube.com/watch?v=mBR-_5dXH4w&feature=youtu.be)? They did an amazing job.
Re: Runnable Sandboxes: Full-stack environments for every GitHub branch
#54Gitlab support in the pipeline?
Re: Runnable Sandboxes: Full-stack environments for every GitHub branch
#55Are active developers determined from repository - or is there another way?