This gist is an implementation of http://sirile.github.io/2015/05/18/using-haproxy-and-consul-for-dynamic-service-discovery-on-docker.html on top of Docker Machine and Docker Swarm.
| Blaze.getView($("div.now-view")[0])._templateInstance.currentAction.get() |
| #!/bin/bash | |
| # Cloud-config for CoreOS IPXE deployment on Vultr | |
| ################################################## | |
| # This cloud-config bootstraps CoreOS on /dev/vda and provisions: | |
| # - private ip-address on eth1 | |
| # - etcd on private network | |
| # - fleet on private network | |
| # - basic firewall (docker compatible) | |
| # - SSHd security hardening | |
| ################################################## |
| source 'https://rubygems.org' | |
| gem 'pact', '~>1.7.0' |
| //----- The ECMAScript 6 meta object protocol (MOP) implemented in ES5 | |
| // This is how getting a property is handled internally. | |
| // Double underscore (__) implies internal operation. | |
| Object.prototype.__Get__ = function (propKey, receiver) { | |
| receiver = receiver || this; | |
| var desc = this.__GetOwnProperty__(propKey); | |
| if (desc === undefined) { | |
| var parent = this.__GetPrototypeOf__(); | |
| if (parent === null) return undefined; |
Why not set backlog on Heroku?
First read this: https://mikecoutermarsh.com/adjusting-pumas-backlog-for-heroku/
Now we're on the same page. Heroku will re-route bounced requests from your dynos but it assumes when this happens that your entire app is saturated. https://devcenter.heroku.com/articles/http-routing#dyno-connection-behavior. Each connection gets delayed by 5 seconds, so you're automatically being docked 5 seconds per request.
If you're setting your backlog to a low value (i.e. if you'll ever actually ever hit backlog) then you'll be in for pain. When you get a spike of requests from slashdot/reddit/whatever you're telling your dynos that you would rather they failed then returned slow responses. So this does mean that some requests will be served, but all the others will fail.
If your app ever hits your backlog (no matter what value it is) it is an indicator you don't have enough throughput and you need to scale out to more dynos. If you set this to an arbitrarilly low value, that point comes
If you want to submit a pull request for an Atmosphere package you will first need to
- On GitHub fork the GitHub repository you want to make changes to.
- Clone the repository to your local machine with the Terminal.
cdinto the folder you want the repository saved in and run thegit clonecommand.- If you do not know the
git clonecommand we break it down into 3 parts. - First part of command is the
git clone.