KLouds short-term development cycles.
- route validation refactoring - business logic stays lean and meaningful
- standalone rancher module - load balancers, reverse proxies, and domainnames
- implement create/rm, up/down, start/stop, logs, scale-- wrap it and lock it down!
- shall be published in npm
- Apps Loader that manages app files
kloud-compose/
└── wordpress
├── docker-compose.yml
└── rancher-compose.yml
- Domain Name is not captured
- Payment leads to an empty dashboard
- show apps & domains & logs
- application icons, descriptions, urls
example directory structure
icons/
└── wordpress.png
kloud-compose/
└── wordpress
├── ...
└── meta.yml
meta.yml format
name: Forky
description: Real time collaborative mind maps
website: forky.io
repository: https://github.com/ds0nt/forky
- tailing the logs into the website's background would be really fucking cool
- our users will have errors/problems. debug user problems? don't fix what isn't broken? hmm, debugging is rather important
Gist totally sucks for these purposes. However, since I have not yet put up the etherpad server, I have forked this gist and made some updates.
Despite the fact that gist sucks for this, this is an incredible idea that I think will drive development. Please consider the user's click-count when comparing this to etherpad.