Comment by instakill | Hacker News Reader

Comment by instakill | Hacker News Reader

Hi.

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 it's up and running?

You provide the octovagrant box, is it secure? Is Vagrant production-ready or is it not part of the production mix? You've got 6 cookbooks listed in the cookbook repo. Do I need all of them? How do I use/install each of them?

What does Docker do? Once I've done all of this setup work, how can I push up all of my code to the desired VPS? Do any of the defaults have security provisions and set up ufw rules to only allow port 80 etc [1], disallow root access, only allow ssh access and all of that goodness? If I use this over manually provisioning and securing servers, do I get sane and secure defaults?

That's a lot of questions, but I may not be the only one asking them, so if I may so bravely ask, ELI5?

[0] Explain like I'm 5 - like http://www.reddit.com/r/explainlikeimfive [1] Just suspend disbelief about my zero-knowledge about setting up servers

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 machines on your local development box. It has nothing to do with production at the moment - it's just for running it locally.

The octovagrant box is pretty open - but that's because it's for running things locally. When it's installed on AWS/DO/Rackspace/Linode/etc. it's firewalled from remote people - but still is pretty open internally. I wouldn't let untrusted people push to it at the moment.

Yes - you need all of the cookbooks, but Packer will take care of that for you - you don't have to really worry about that.

If you're just using the AWS AMI that we've already built - then you can really ignore Packer and Chef - just launch the AMI and you're done.

Docker allows you to run processes inside of a container. So you can launch a set of processes from your source code and have it run on its own.

Once it's setup, you merely add a remote git target, push your code to the server and it builds and launches the code that you have pushed. It works like Heroku for simple websites.

That help at all?

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!

Same here. I'm waiting for clean and nie solution to utilize all spare hardware, I have in my company. It would be great to have simple PaaS running on one machine, it would be awesome to utilize them all. If someone could give me step-by-step instructions / solution how to do this, I would really pay for that (or support open source, if that's the case).

Checkout CoreOS + Deis

The knife solo page should help with this:

http://www.octohost.io/knife-solo.html

I don't think so. Why would I need vagrant on the server ? ~/octohost-cookbook$ sudo rake knife_solo user=root ip=172.16.90.151 rake aborted! Kitchen::UserError: Vagrant 1.1.0 or higher is not installed. Please download a package from http://downloads.vagrantup.com/.

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

Reply on news.ycombinator.com