Everybody knows de difficulties of managing content when using staging for his website. To tackle that problem I started writing my own sync module and when I created a project page for it on drupal.org, one of the first issues created was stating that the Deploy module was practically the same thing. After checking out the deployment module myself I had to agree with that.

Since I discussed this issue up front with a lot of people and no one even mentioned this module it is clear that this really wanted module is just unknown.

So spread the word and start testing the deploy module.

The deployment framework is a series of modules which are designed to allow developers to easily stage Drupal data from one site to another. This includes content (nodes, taxonomy, users, etc) as well as configuration (views, content types, system settings, etc.) Not only can it push new content, it can also push updates to existing content. Deploy automatically manages dependencies between nodes (IE nodereferences) as well as between other objects. It is designed to have a rich API which can be easily extended to be used in a variety of situations. Check out the screencast for a demo!

I was creating a new website for a customer and I thought imagefield_gallery would be a nice to have. Since the module didn't have a drupal 6 version, I ported the module to D6. Today I released the patch at http://drupal.org/node/299122#comment-1691890

Please test and comment.

In order to get the service more error prone, I added some logic to disable erroneous websites. Websites are disabled when the two last checks failed and in total 75% of all checks failed.

Users are able to re-enable the site by just editing the entry in their list. At that time the website is verified, and when successful it is enabled again.
This update will also be applied on the cron module.

I just added a new module to drupal.org: password_trigger. With this module an email notification is send to the user of who the password is changed.

An administrator can configure the email, as every user email, at admin/user/settings.

You can find the new project at: http://drupal.org/project/password_trigger

After the update of drupalcron to support the cron_key for drupal 7 it is time to apply those changes to the cron module.
Also the added curl options at drupalcron are added to the cron module.

Today I had some time to update drupalcron.

Bugfixes:
Change of curl options to solve problems with unreachable sites

New features:
Support for drupal 7 cron. You're now able to add the in drupal 7 added cron_key.

Has anyone a clue on this one ?

sudo cat /proc/sys/fs/file-max
1048576

sudo cat /etc/security/limits.conf
* soft nofile 1048576
* hard nofile 1048576

sudo cat /etc/sysctl.conf
fs.file-max=1048576

ulimit -n
1048576

But yet when my service starts at boot:

sudo cat /proc/pid/limits | grep files
Max open files 1024 1024 files

Whenever I restart my service everything is ok:
sudo cat /proc/pid/limits | grep files
Max open files 1048576 1048576 files

This is running on a Debian Etch with kernel 2.6.28

Today I noticed that the 100th site was subscribed to Drupalcron.org.

Hopefully this is only the first milestone we could reach with this service.

One thing is sure, the idea is a success. Not only is there the admintools module that enables you to do the same as Drupalcron.org for your own, Acquia made this also a feature of their 'Acquia drupal'

At request I've added the cron module to drupal.org. It's named admintools, cause I plan to make more tools for the admin of several drupal installs. So more news will follow soon on that.

A drupal 5 version of the cron module will follow shortly.

You can find the module at: http://drupal.org/project/admintools.

After speeding up some things, it's time to attract a bigger audience. Drupalcron.org will provide the drupal admin with a cron visit every hour. No more cron configuration. Just create an account on Drupalcron.org and you can add 5 drupal sites to your user account.

If you administer more then 5 drupal sites, and yet you want central administration and still no cron configuration you can download and install the cron module. This allow you to add countless sites, to be visited when the cron of the on which the module is installed is executed. If you add that site to Drupalcron.org, all your sites crons will be executed every hour, without any configuration of cron.