galaxy
galaxy copied to clipboard
litl
Docker Micro-PaaS
Is it possible to pass an entry point to the deploy command ? Example: commander -env test app:deploy app1 xxxxxxxx.dkr.ecr.us-east-1.amazonaws.com/service:01 /usr/bin/entry --get-secrets-keys
I believe this is happening because I manually added an application to shuttle. I launched a docker container by hand (due to #272) and then `PUT` a config to shuttle...
Is it possible right now? I need to start an application that mounts a volume into the running docker container using docker's `-v` flag.
We currently can't do rolling upgrades of the galaxy image because the apps often take longer to deploy than the instances. Galaxy needs to lookup all applications that should be...
We currently roll out deployments as fast as we can through the cluster, but we have no way of synchronizing those events, which leads to a mix of versions running...
Galaxy (the `galaxy` command) tried to manage the physical pools via aws cloudformation. This mixing of configuration, code, and dependency on AWS specifics has made for a large amount of...
Use Consul for configuration and service registration. - Unify runtime configuration and app configuration into a single file. Each config will have everything needed to run a single service, including...
We should support webhooks for certain events. Among them: - Code deployments - Backends registered and unregistered With these we could send notifications to Slack and track when deployments happen...
If you set ports or vhosts with `commander runtime:set` there's no way to see them, because they're not really tied to a "runtime pool" and that's what `commander runtime` iterates...