Runnable Sandboxes: Full-stack environments for every GitHub branch • Hacker News Board

Re: Runnable Sandboxes: Full-stack environments for every GitHub branch

#41

Post by bliti » Thu, Mar 17, 2016, 6:04 PM UTC

kernel_panic wrote: post #33

bliti wrote: post #28

Earlier quoted context omitted.

What's your stack like? For those interested...

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…

Interesting. I haven't worked a lot with Nodejs (Haven't really gotten to it), but have with the rest of the stack. I'm into messaging and networking. Maybe drop me a line?

Re: Runnable Sandboxes: Full-stack environments for every GitHub branch

#42

Post by dtertman » Thu, Mar 17, 2016, 6:23 PM UTC

This sounds neat - are there plans for an on-prem version instead of EC2? We have Mirantis OpenStack running in a bubble at my organization (we are cloud-averse).

Re: Runnable Sandboxes: Full-stack environments for every GitHub branch

#43

Post by gingerlime » Thu, Mar 17, 2016, 6:31 PM UTC

kernel_panic wrote: post #39

gingerlime wrote: post #37

Looks like exactly what we're looking for. Why is it only available with a Github organization account though?

Support for other code repositories is on our roadmap — we are looking to hire more developers to help build support for them ! :)

We are using github, but just not github organizations...

Re: Runnable Sandboxes: Full-stack environments for every GitHub branch

#44

Post by ykumar6 » Thu, Mar 17, 2016, 6:43 PM UTC

dtertman wrote: post #42

This sounds neat - are there plans for an on-prem version instead of EC2? We have Mirantis OpenStack running in a bubble at my organization (we are cloud-averse).

It's on our roadmap. Can you submit a support ticket and I can fill you in over email

Re: Runnable Sandboxes: Full-stack environments for every GitHub branch

#45

Post by ykumar6 » Thu, Mar 17, 2016, 6:50 PM UTC

gingerlime wrote: post #43

kernel_panic wrote: post #39

Earlier quoted context omitted.

Support for other code repositories is on our roadmap — we are looking to hire more developers to help build support for them ! :)

We are using github, but just not github organizations...

The reason it's built for Github organizations is we can access-control your private infrastructure based on the permissions set in Github.

We don't have access to the same APIs with just a personal accout

Re: Runnable Sandboxes: Full-stack environments for every GitHub branch

#46

Post by donatj » Thu, Mar 17, 2016, 6:54 PM UTC

This looks very promising. I wonder if/how well they could handle a 500gb database.

Re: Runnable Sandboxes: Full-stack environments for every GitHub branch

#47

Post by ykumar6 » Thu, Mar 17, 2016, 6:57 PM UTC

donatj wrote: post #46

This looks very promising. I wonder if/how well they could handle a 500gb database.

Founder here - We absolutely can! Just give us a heads up so we can make sure it loads up properly on your account

Re: Runnable Sandboxes: Full-stack environments for every GitHub branch

#48

Post by callumlocke » Thu, Mar 17, 2016, 6:57 PM UTC

Can someone help me understand what's the difference from Travis CI, Circle CI, etc?

Re: Runnable Sandboxes: Full-stack environments for every GitHub branch

#49

Post by ykumar6 » Thu, Mar 17, 2016, 6:59 PM UTC

callumlocke wrote: post #48

Can someone help me understand what's the difference from Travis CI, Circle CI, etc?

Travis CI and Circle CI push code to a staging or production environment. So you still need to setup a full-stack environment to do end-to-end testing.

Runnable let's you have end-to-end (full-stack) environments with every branch. The minute a branch comes up, you have an environment. This includes a clone of your database

Re: Runnable Sandboxes: Full-stack environments for every GitHub branch

#50

Post by mbrock » Thu, Mar 17, 2016, 7:19 PM UTC

kernel_panic wrote: post #35

mbrock wrote: post #31

Earlier quoted context omitted.

Do the stacks run with Docker Swarm and Docker Networking? If so, does it work well? Any strange issues you had to work around, etc?

Our stack does use swarm under the hood. So far we have not seen any major issues with scheduling across 100 servers. However we have seen issues with the swarm event stream disconnecting. Our workaround was connect to the event stream of the docker engines directly and use the `since` parameter. We currently use weave net to handle docker networking and have not had major issues with it.

Nice to hear!