darron

5 ms·

1.
by darron 12y ago
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 a
2.
by darron 12y ago
octohost is like a mini personal Heroku. Packer is a tool that helps to build the image that octohost runs on. It installs all of the software needed and prepares the VM it runs on. Vagrant is a tool that allows you to run different virtual
3.
by darron 12y ago
Chef is being used to build the VM and put the entire thing together. But after it's built - you never need to use Chef again. Fig didn't exist when I started this and I wanted to mirror the git push that Heroku used. Logging is h
4.
by darron 12y ago
Finally allowed back in - HackerNews locked me out because I was "Submitting too fast." Needed more karma.
5.
by darron 12y ago
The knife solo page should help with this: http://www.octohost.io/knife-solo.html
6.
by darron 12y ago
I have been using Chef for a number of years. I started this project with Ansible because I wanted to learn how to use it. As I went along, I wanted to learn more about TDDing Chef cookbooks with Test Kitchen so I switched back to Chef.
7.
by darron 12y ago
There's an entirely explained version here: http://www.octohost.io/aws-install.html I should link to it from the homepage - that will be added shortly.
8.
by darron 12y ago
You don't need a cloud. You can deploy it on whatever hardware you have as long as you have an SSH connection: http://www.octohost.io/knife-solo.html
9.
by darron 12y ago
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?
10.
by darron 12y ago
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 Dockerf
11.
by darron 12y ago
That's the goal - but I was working on this on weekends mostly by myself and I think they have a team working on it full time. Deis is a much more mature choice and is based on CoreOS which is awesome.
12.
by darron 12y ago
At the time we started, I wasn't happy with running some of the base items inside of Docker. I'd likely change that today if I was starting now - but that was in November 2013 when Docker was much more beta.
13.
by darron 12y ago
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 - wit
14.
by darron 13y ago
This is pretty awesome. Never heard of them until today - looks interesting.
15.
by darron 13y ago
We're building a backend using Docker that can do just that. It's called octohost and there's lots of information available here: http://www.octohost.io/ We have a static template that you can see here: http