kernel_panic
Re:Introducing Kontainer: The Easy Way to Switch to Kubernetes
on Tuesday May 23, 2017 @02:39PM (#14403939)
oops, your right! updated the post :)
Re:Weave and Docker for Mac: The bridge between local and remote services
on Tuesday April 12, 2016 @01:37PM (#11481693)
We have around 18 different microservices each with their own configuration and repos. Setting them all up, keeping them up to date and managing them locally is a pain (and also turns my laptop into an inferno). Our staging environment is on Runnable which spins up all 18 of these in an isolated stack so I do no have to worry about configs or management.
Re:Runnable Sandboxes: Full-stack environments for every GitHub branch
on Thursday March 17, 2016 @03:53PM (#11307065)
Responded in another thread here: https://news.ycombinator.com/item?id=11306045
Will be happy to go into more detail.
Re:Runnable Sandboxes: Full-stack environments for every GitHub branch
on Thursday March 17, 2016 @01:52PM (#11306163)
Support for other code repositories is on our roadmap — we are looking to hire more developers to help build support for them ! :)
Re:Runnable Sandboxes: Full-stack environments for every GitHub branch
on Thursday March 17, 2016 @01:36PM (#11306045)
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.
Re:Runnable Sandboxes: Full-stack environments for every GitHub branch
on Thursday March 17, 2016 @01:12PM (#11305780)
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 Machines + Swarm is used to schedule and run applications. Docker Registry is used to store images. We use WeaveWorkes weave for inter-container communication.
We are starting an engineering blog as well, keep posted for deep dives into our architecture! http://blog.runnable.com/
Re:Runnable Sandboxes: Full-stack environments for every GitHub branch
on Thursday March 17, 2016 @11:50AM (#11305107)
Bitbucket is on our roadmap, just collecting feedback (and hiring developers) to see if we should deliver it sooner
Re:Wilson's Algorithm
on Saturday June 14, 2014 @05:07AM (#7892410)
can you someone edit it and make it better?
http://runnable.com/U5wQt8xHLYsVkYc_/wilson%E2%80%99s-algori...
Re:HTTPie is a command line HTTP client, a user-friendly cURL replacement
on Saturday June 14, 2014 @04:57AM (#7892397)
This is amazing! Will definitely be switching away from using curl.
I put a the basic examples here to easily play with httpie
http://runnable.com/U5wOrMxHLYsVkYbX/basic-httpie-examples-f...
Re:Mprpc: A fast Python RPC
on Saturday June 14, 2014 @04:34AM (#7892373)
Sweet! was playing around with it @ runnable
http://runnable.com/U5wIq8VhhNkI6vb2/basic-mprpc-example-for...
Re:Butterfly: Your everyday terminal in your web browser
on Saturday March 01, 2014 @02:31PM (#7325738)
This is really cool! Would be great to get this on places like http://www.runnable.com