We have spoiled you with many new features in recent weeks, but I suspect that today’s announcement is likely to be the hit… For a few days now, new shared accounts, VPS and dedicated servers are running on our brand new software infrastructure. What does it bring us? Let’s find it out.
Our new infrastructure runs under the latest version of Debian (Jessie), which brings an update of all software and libraries available, from git or Vim to Apache or Java. Software and languages have also been added, such as Go or R.
But the heart of the change is Python and Ruby: we have evolved our package management to no longer depend on the versions proposed by Debian, which allows us to offer:
- For Python, from version 3.6 to 3.3 and 2.7 to 2.4.
- For Ruby, from version 2.4 to 1.8.7.
- For PHP, nothing changes: we were already offering the latest version (7.1), and we keep all the versions since 5.2, and even 4.4 for the (slightly) latecomers.
Whether for Python or Ruby, the installation of packages (via pip or gem) required some efforts, minimal but sometimes confusing for the least experienced. It was sometimes necessary to specify an option or define an environment variable, or even create a file (.bash_profile) for new commands to be executed directly.
Now pip install and gem install work directly without any configuration. Even better: you will not even need to add any path for your applications to find libraries: it is automatic.
We also thought of PHP and its PECL extensions: indicate in the command ad_install_pecl (a home-made script) the name of the PECL extension you want to install, it will deal with the download/configure/compile steps: all you will have to worry about is uploading the .so file from the section Environment > PHP in the alwaysdata administration.
Again, this applies mainly to Python and Ruby: so far, some libraries were installed globally on our systems, including Django and Ruby on Rails. This posed a number of problems, so we decided to remove them. You will now start with a pristine environment, but we saw in the previous section that installing libraries was now trivial.
WSGI (Python) or Ruby Rack and Ruby on Rails sites were managed by Apache (via mod_wsgi or Passenger). They are now managed by uWSGI, an application server with several advantages. This change is largely transparent for our customers, but new options (all optional) appear in the configuration form of a site:
- Force a particular version of Python or Ruby.
- Environment variables to be defined.
- Working directory.
- For Python, the virtualenv to be used.
- For Ruby, use the application’s Gemfile.
This new infrastructure paves the way for supporting new languages, in particular for running web applications. Node.js will definitely be the first, but others should follow very soon.
Right now, by opening a new shared account, VPS or dedicated server. Older customers will have to wait a little longer: we are preparing the migration phase that will start in the coming weeks, together with the migration to our own hardware infrastructure (for the oldest shared accounts). Every customer will be notified by email beforehand and will have at their disposal:
- A documentation page listing major changes that may cause incompatibilities.
- Tools to partially simulate their account under the new infrastructure.
The more adventurous, however, can ask for a migration via a support ticket now, but at their own risk and without the possibility of going back. Needless to say, if you have anything in production, go your way and wait for the official migration. If you want thrills, jump in parachute.
We designed this new infrastructure to be much more flexible than the previous one, and no longer find ourselves in a situation with old software. Although we cannot always offer the latest versions as soon as they are released, for many reasons (lack of stability, blocking bugs, unavailable dependencies), this new flexibility will allow us, for example, to reduce the wait for Python 3.7 and Ruby 2.5 to just a few days!