Dockerized Cloud9 IDE with auto-mounting
Features
- Fully customizable dev environment
- Git integration
- Debugging
- Integrated console
- Accessible from anywhere
- Designed to easily adapt to any workflow
Getting Started
Clone this repo to your dev box and enter the directory you cloned it into:
git clone https://github.com/briansrepo/dockerfiles && cd dockerfiles
Now launch the Docker container:
DIRECTORY=[directory] MYUID=$UID docker-compose -f nginx-proxy.yml -f cloud9.yml up -d
The [directory] variable should be set to the directory containing the code you want to work on. For example, I might enter "DIRECTORY=/home/brian/projects/acme.com". The MYUID=$UID sets the internal ownership of the docker file system to the system ID you are currently logged in with. This ensures the files you create and edit in the mounted directory will be owned by you.
Now make an entry on your local host file with your server's IP address and the domain 'cloud9.dev':
123.45.67.89 cloud9.dev
At this point, you can pull up a browser and go to http://cloud9.dev to find your full development stack waiting for you. You can also run this container locally and access it by entering "0.0.0.0 cloud9.dev" in your local host file. Note: This won't work if you have anything else running on port 80, including Apache. You can find the rest of the files I use to manage my LAMP workflow in my lavalamp repo.
Why?
I wanted the benefits of being able to pull up an IDE with a consistent interface and feature-set on my server no matter what machine I'm working from. I decided to set it up as a Docker image for easy deployment and cross-platform consistency. If my dev box and servers all exploded simultaneously, I could potentially be back up and coding in minutes.
After a lot of research and experimentation, I decided to go with the excellent Cloud9 service. They were the only online IDE I found that offered the features I wanted, including integrated console and debugging, along with a publicly accessible repo. There are a few Cloud9 Docker images out there but they didn't quite fit into the workflow I had in mind, so I ended up rolling my own solution. I based it on Phusion's stripped down version of Ubuntu. I run Cloud9 in the foreground as a child of the main runit process. You can see a great analysis of why that matters in Phusion's README.
For domain name resolution I use jwilder's automated nginx reverse proxy. It searches for a Docker container with a VIRTUAL_HOST environment variable that matches the domain name of the request. If it finds one, it forwards the request to it. Easy peasy.
Written with StackEdit.