Simple web-focused Docker-based mini-PaaS server

Re:Simple web-focused Docker-based mini-PaaS server by tokenizerrr on Friday July 25, 2014 @12:43PM (#8086125)

Is 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)

[ Parent | on HN ]

Re:Simple web-focused Docker-based mini-PaaS server by darron on Monday July 28, 2014 @12:26AM (#8095181)

This is mainly focused on websites, but you can launch other items that don't require any ports exposed:

http://www.octohost.io/data-stores.html

I added some "magic" Dockerfile comments - this is the one to add in order to not expose anything via HTTP:

NO_HTTP_PROXY

I am not a huge fan of volumes where data is stored on the box - but you can do it the same way I've described on the page.

I think of octohost boxes as app servers - if you have data on it, you should likely have it stored elsewhere. I've used Heroku to store additional data sometimes:

http://blog.froese.org/2014/03/17/using-octohost-with-heroku...

We've also used remote MySQL servers:

https://github.com/octohost/mysql-plugin

There's lots of ways to do it.

[ Parent | on HN ]