Running Fedora 25 and want to give Eclipse Che a test spin? It’s far easier than you may think.
The steps are simple but quite important they are followed closely. Best to always follow the official process, right? In that spirit, the instructions for getting Docker running on Fedora were quite straightforward. Use those to make sure you’re running Docker smoothly.
As advertised on its homepage, getting Che installed is as simple as a single command: docker run eclipse/che start
Next comes the simple but tricky part. On Fedora 25 I figured out that I couldn’t use the shortened Docker command – I needed to run the full explicit one specifying paths. I didn’t want to have to remember this, and I also wanted to make sure Docker was running whenever I needed to run Che, so I created the following bash alias to use:
alias che='sudo systemctl start docker && sudo docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock -v /home/ennenine/Development:/data eclipse/che start'
Now whenever I want to spin up Che and start working, I simply have to type che into the nearest terminal.
Recently I’ve been working a new project called ‘Lunchbox’. Basically, it is a GUI wrapper around vagrant projects so that you can use the power of vagrant and virtual machines without the learning curve. To start with, I’m targeting support for DrupalVM.
Here’s a quick status update of the project to date. It’s still not ready for prime time, but this will give you an idea of where the project is headed. If you’re a bleeding-edge kind of person or would like to contribute, head over to the Lunchbox project page and submit some PRs!
DrupalVM is a great project with some very complete documentation. However, for some reason I kept having difficulty getting it to work on Ubuntu despite seemingly straightforward instructions including a reference to DigitalOcean documentation (usually very good) about getting NFS running on Debian/Ubuntu.
After a few mis-starts, I think I have found the magic combination to getting it all running on a new Ubuntu-based system. As with most things, it seems incredibly simple in hindsight. One major prerequisite is that NFS does not work reliably with home directory encryption turned on. If you must run with this you’ll have to turn off NFS support in DrupalVM. Once you have that squared away, here’s the basic process:
sudo apt-get update
sudo apt-get install nfs-common
apt-get install nfs-kernel-server
sudo apt-get install virtualbox – you may need to make sure your software sources is configured correctly, usually needs to include Canonical Partners
The key pieces, I’ve found, are installing the
nfs-common package and the
The end result is a DrupalVM with NFS (much more performant) with magical DNS capability (via vagrant-hostsupdater, no need to edit
/etc/hosts). If you add new sites to the config file just run
vagrant provision to quickly get them configured in the VM and added to your local DNS without losing anything else or needing to wait for a full VM rebuild.
One more pro-tip: mimicking the Acquia cloud platform is super-simple with DrupalVM since it includes a yml override file to match Acquia’s hosting environment.
I’ve created a series of screencasts on how I set up Sublime Text to do development work. While I do mostly Drupal development, these videos are not necessarily Drupal specific and can be used for most any web development.