You should add comments to your example to explain what each step is doing.
Simple web-focused Docker-based mini-PaaS server
11–20 of 34 posts
Re: Simple web-focused Docker-based mini-PaaS server
#12How does that compare to dokku?
Dokku was the inspiration for it. I wanted a simple way to deploy small websites and I really wanted to understand how it all worked together - so I built my own.
One major difference (like already mentioned) is that I wanted to use Dockerfiles rather than Procfiles. I wanted to have full control over how it built and ran - and I didn't want to go through slugbuilder / buildstep at the time.
It may actually be easier on end users to use Heroku buildpacks and abstract some of the magic - but for our uses Dockerfiles were the best fit.
Now, the Tutum team came out with something that even simplifies it even more - and it might be worth looking at:
http://blog.tutum.co/2014/04/10/creating-a-docker-image-from...
I have had that on my backlog for several months and just haven't had time.
Re: Simple web-focused Docker-based mini-PaaS server
#13You should add comments to your example to explain what each step is doing.
If you're talking about this:
http://www.octohost.io/screencast.html
Then I have detailed what happens more thoroughly here:
http://www.octohost.io/theory-of-operation.html
That help?
Re: Simple web-focused Docker-based mini-PaaS server
#14why the move from ansible to chef?
Re: Simple web-focused Docker-based mini-PaaS server
#15Hi. Let's pretend that I'm an intermediate developer with no knowledge about sysadmin or even deployments. How would you break this down and ELI5 [0]. How does Packer fit into all of this (assuming I'd use Digital Ocean). What's Vagrant for? What does Virtual Machine do here? Do I need these three machines on the target VPS or only on my local development machine? To add my DO keys do I need to ssh into vagrant once…
Yeah - currently deploying it from scratch is a little too hard for most people. I'd like to fix that, but just haven't had the time. I'd honestly love a system that deploys the image for you to the cloud of your choice - with setup for ssh keys and things to make it simple. Just not in the cards timewise at the moment.
FYI not everyone wants to run this in "the cloud". I have a LOT of bare metal and want to deploy something like this on bare metal. Please don't forget us users who buy our own hardware!
Re: Simple web-focused Docker-based mini-PaaS server
#16Is this only for websites? I'm assuming it just executes the dockerfile, and uses the run command. I have set up a hacky bash script myself to do this, but also use it for daemons which don't need to expose any ports.
The theory of operation page hints that if no ports are exposed, then the container isn't launched. It would be great if the following would be possible:
1) No ports exposed. Just run some software and that's it.
2) Expose one or multiple http ports with different domains for each.
3) Expose one or multiple tcp/udp ports, which get mapped directly to a host port.
I also can't see if there's any support for volumes, but if not, that also seems fairly important.
For what it's worth, here[1] is how I handled it, but the project is very sloppy and I do not recommend it's use to anyone since I'm looking to switch ;)
[1] https://github.com/r04r/dockah/blob/master/dockah.sh#L35 (reads a config file like https://gist.github.com/r04r/d5d0ea6506824e2cf6d9)
Re: Simple web-focused Docker-based mini-PaaS server
#17why the move from ansible to chef?
Because Chef is awesome? (no real answer here, just a fan)
Re: Simple web-focused Docker-based mini-PaaS server
#18Could you elaborate on what you are using chef for and why you didn't use something like fig.
I'm getting a bit overwhelmed by the number of meta tools around docker deployment.
Also, and most importantly, how are you handling logging? Is it being persisted on the host volume or is rsyslog-streamed
Re: Simple web-focused Docker-based mini-PaaS server
#19why the move from ansible to chef?
I'm curious about this as well – for the most part you usually hear about people having moved to the other way, from Chef to Ansible (personally, still using both).
Ansible also (currently) seems a bit more suited for the Docker workflow, so I'd be interested to hear about the developer's experiences with this.
Re: Simple web-focused Docker-based mini-PaaS server
#20How does that compare to dokku?
Dokku was the inspiration for it. I wanted a simple way to deploy small websites and I really wanted to understand how it all worked together - so I built my own. One major difference (like already mentioned) is that I wanted to use Dockerfiles rather than Procfiles. I wanted to have full control over how it built and ran - and I didn't want to go through slugbuilder / buildstep at the time. It may actually be easier…
Thanks for the mention! I'm part of the Tutum team, and we actually made an open source project called Boatyard.io
It's basically a web UI that builds images from tarballs, dockerfiles, and github repos. We use it internally all the time and we thought we'd contribute back.
You can find our post about it here:
http://blog.tutum.co/2014/05/26/introducing-boatyard/
Great job on octohost.io!