I have been using the on-line development environment at codio.com for some time now, initially for personal projects and investigations but increasingly for work related coding and training purposes as well. One great feature is that the free account provides you with more than enough to work on a project or investigate or investigate new technologies.
Soon after I began playing around with Drupal 8 for the first time I was delighted to discover that a Codio project packs enough power to realistically work with Drupal, Codio became the perfect place for me to work on my code and investigations any time I had a few minutes spare and a wireless network connection.
I shared my enthusiasm for Codio with a few fellow developers at our local Drupal user group, although Codio backs each of your projects with a ‘box’ that gives you a server like environment there are a few differences from a normal Drupal install so I laid out the steps required in my Drupal 8 blog.
There were two further problems however, firstly the rapid development of Drupal 8 (in alpha at that point) meant that I was killing and bouncing up new Codio projects at quite a rate (at the time you couldn’t make a deep copy of a Codio project), secondly there were people who wanted to start learning who found the set-up process a little daunting.
For convenience, both for myself and others I decided to put together some scripts that could be used to completely automate the Drupal install and set-up on Codio, wrote a more general post about Codio and Drupal development and put my scripts up on Github.
Since the release of Drupal 8 beta 1, I have modified to allow any particular tag from the Drupal code repository to be used (which also enables older versions of the CMS to be used). I have also addressed one issue and one pull request from other Github users.
When I have the opportunity and the need I will improve a little more, there are some todos at the bottom of the project README.md
The project is a success in that I have a very quick and light-weight route to firing up a Drupal project that compliments a more medium-weight approach using virtual machines.
What this demonstrates
There is nothing particularly difficult in this project, a little shell scripting, a little Git work and understanding of Drush etc. is all. However I believe that despite its modest nature it does demonstrate:
- my healthy developer need to automate the drudgery
- some level of willingness to share and help other
Although tiny in the scheme of things, the project has been forked a time times, and appreciative comments have been made on social media, which considering it now saves me time has to be a win.