New Drupal 6.6 installable live CD released
lirazsiri - October 31, 2008 - 07:40
The TurnKey Linux project is proud to announce the release of TurnKey Drupal 6, a lightweight, installable live CD of Drupal 6.6, which can run on real hardware in addition to most types of virtual machines.
Out of the box, TurnKey Drupal is designed to provide users with a ready to use, turn-key operating system environment that is carefully built from the ground up with the minimum components needed to run Drupal with maximum usability, efficiency and security.
See screenshots.
Highlights
- beautiful web management interface (Mac OS X themed)
- easy to use configuration console (written from scratch in Python)
- minimal footprint (159MB)
- based on Ubuntu 8.04.1 hardy LTS
About TurnKey Linux
TurnKey Linux is an opensource project that aims to develop high-quality software appliances that are easy to deploy, easy to use, and free. Our motto is "everything that can be easy, should be easy!"
More about us on our homepage.
Why is update.module disabled by default?
This looks slick. However, when I read the release notes for the Drupal 6.6 appliance, I found this:
It's not clear to me what the apt package manager is doing that is breaking update.module, but I'd love to hear about it. ;) Is it checking out source directly from CVS? If so, you could include CVS deploy in your appliance and then everything should Just Work(tm). If it's neither getting the code from CVS nor the tarball, where are you getting it? ;)
Anyway, it'd be a shame to have a bunch of sites deployed that have update status notifications disabled, both for the security of site owners, and for the accuracy of the project usage statistics that are now visible on this site.
Cheers,
-Derek
it's checking out updates
it's checking out updates right out of their repositories.... thus updating drupal the same way as the operating system. (almost completely automatic)
it's getting the code from .deb packages (sort of...)
and those confusing announcements are for example:
Current version: 6.x-1.x-beta2
New Update: 6.x-1.x-beta1
Why we disabled update notifications
We disabled the status notifications because they produced annoying and obtrusive false positives that would scare new users when used with the Debian sid package.
When a security issue comes out Debian will often backport security fixes rather than upgrade to a newer version and risk breaking an existing installation. The status module doesn't know about this so it raises the alarm anyhow.
Debian's way actually makes a lot of sense as security updates can be applied to an existing installation automatically by the package manager (apt) - there is much less risk of introducing an incompatible change (e.g., database schema change) that will require manual intervention by the user.
Requiring manual intervention to apply security updates kind of circumvents the whole point of an appliance - a blackbox that just works.
Cheers,
Liraz