This is the first public release, under GPLv3. The software is now in a state where I can use it every day to maintain chroots. To download the source code, use the link below. There is also a git repository available for cloning. Chroots is developed under Ubuntu, and can build debian and Ubuntu chroots through deboostrap.

Source Code: chroots-0.2.tar.gz
Git Repository: http://git.digitalself.org/?p=chroots.git

If anyone finds this useful, don’t hesitate to drop a comment with suggestions or feedback. I’m looking forward to it. Bug reports are nice, and will be handled. More information about chroots below, and inside the source package. In time, I might put up a page for the project. In the meantime, enjoy this release.

About Chroots

Chroots is a set of wrapper scripts around  debootstrap. debootstrap is an effective way of create a general purpose build environment. While it is fairly simple to setup a working environment, it’s always necessary to perform several steps to actually login into a deboostrapped environment using chroot. It can be a cumbersome task, hence chroots.

For test building packages there is already pbuilder. What pbuilder does is build a debian package in a freshly created chroot environment. This allows detecting build and dependency errors quite effectively. Nevertheless, to use pbuilder, an environment is setup every time and out of the user’s reach, and it is quite a difficult tool to use for the occasional packaging experiment.

This is where chroots comes in. It allows to easily configure setup and deploy a chroot environment, enabling everything from package tests to dependency check, or manual tarball compilation, keeping your production environment ‘clean’. It allows to maintain several chroot environments at the same time, so that it can be easy to test multiple systems.

How to develop a WordPress theme without major hassle ? Or a php website for that matter ?

Option 1

Deploy a local http server, and test it as you code it on your local machine.

Downsides

• Requires deployment of local http server and mysql server and wordpress/custom stuff.

Upsides

• Fast code/test/fix cycle.
• If you screw up, just reinstall or star over.
• Does not bother visitor on production sites.

Option 2

Code directly on the server. Through ssh.

Downsides

• Remote work is usually slugish.
• Requires exporting the X windows for minimal usefulness.
• Too much work to get into a usable state.
• Direct work on the database/project/software.

Upsides

• Direct work on the database/project/software.
• Already deployed server/php/mysql/wordpress whatever software.

But I recently found a third option that seems viable.

Option 3

Mount the remote working directory through sshfs.

Downsides

• Remote work can be slugish.
• Direct work on the database/project/software.

Upsides

• Direct work on the database/project/software.
• Simple deployment. Just mount the damn thing and be on your way.
• Take advantage of your desktop/development environment.

This is the latest and greatest solution so far. But this still doesn’t sound like perfect, because if I want to code a wordpress theme/template I have to enable it and work on my production website, which hinders both development and visitors.

Has anyone got a great solution for this ? A great workflow ? Or am I just being lazy and should install everything locally ?