A write-up of the talk on Drupal 8 and the site building features in core, from DrupalCon Prague.
Might be useful? What kind of a title is that? Surely it *must* be useful??
How do I access my server with FileZilla on a Windows PC?
You must have used PuTTY to generate your SSH keys. If you did not do that, go and follow the PuTTY steps here before continuing.
How do I access my server terminal from a Windows PC?
Depending on how you generated your keys, the answer will be different. If you have any problems with logging in having followed these instructions, then please make a note of the error message and raise
How do I create an SSH public key for a Mac OSX/Linux PC?
Mac and Linux users should follow this excellent guide by GitHub: https://help.github.com/articles/generating-ssh-keys
Are your systems Drupal-specific?
No, not at all. Obviously we have tweaked the various settings of PHP, Memcached, MySQL, and so on to be optimised for Drupal, and we have common configurations in place for Nginx and Varnish to run Drupal websites, but under the hood our stack is a standard drop-in replacement for LAMP.
Information on where Code Enigma servers are located.
It depends on what you purchase.
What are the components of your High Performance Stack for Drupal?
Essentially, it’s a LAMP equivalent (Linux, Apache, MySQL and PHP). But it runs Drupal really, *really* fast. The key components are:
How does your Managed Server product actually work?
We don't just provide ready-to-go virtual machines optimised for Drupal. We also provide server management - in fact, many of our customers run their own hardware and employ us to manage the software running on it.
Our set-up is really cool!
As it happens, yes. We have packaged and priced a set of servers designed to get a pro Drupal development company off the ground, with its own ticketing, VCS (Git), continuous integration, development, stage and live application servers. You can buy some (e.g.
Can we use your continuous integration service on our own servers?
Technically, yes. Certainly, if we manage your server for you.
Do you support Drupal 8?
Yes! We've been working at this, while our Drush version doesn't support Drupal 8 out of the box, we can replace Drush on a server-by-server basis to the latest version and Drupal 8 is now supported by the latest version of Drush.
Do you support the use of install profiles for builds?
Yes, our continuous integration supports Drupal install profiles. If you need a build to run using an install profile, just let us know when you order and we'll make it so.
Do you fully support multi-site Drupal applications?
Yes, we do. What more can we say?
Do you support a dev -> stage -> live workflow?
We go one better. Because we don't have a "platform" per se we can create as many environments as your deployment workflow requires. Typically our own development teams have four:
We provide continuous integration with Jenkins when deploying changes to sites. This FAQ details the requirements to use our CI scripts.
Yes, but nothing too scary, and we can help you out with the set-up. The main requirement is the file structure in your repository - note, <directories> are denoted like HTML tags to distinguish them from files:
Where do I have to keep my code if I want to use your continuous integration service?
You may keep your code in any Subversion or Git repository you like.
Sometimes, a build just doesn't go right. This FAQ explains how to roll back a bad build.
Our scripts take a back-up the instant before taking the site offline, then check out/clone the latest code into a *new* directory and update a symbolic link to point to that new code.
Why can't I install Drupal from a browser?
Because we block any scripts in Drupal that could potentially be exploited. We strongly advise you use the command line tool, Drush, to install new copies of Drupal. Having logged in to a terminal, run commands similar to this:
How do Code Enigma provide continuous integration?
We use a piece of open source software called Jenkins.
What is continuous integration? It's magic!
Continuous integration is actually, technically, the process of making many code merges a day in a busy development team to avoid car-crash scenarios at the end of cycles of work.