So the Sweetcron documentation isn’t altogether clear on what you should put in cron for it to update automatically, rather than slowing down a user every 30 minutes.

It’s fairly intuitive, but for those missing this logical step, do the following.

Change the setting in the admin panel from psuedo-cron to true-cron, and take note of the URL.

Then put the following in your crontab file (easily accessed with ‘crontab -e’ on a debian machine):

You can change the 5 to be the number of minutes between updates that you want, and you’ll definitely want to change the URL to the one listed in your Sweetcron’s admin page.

I use git for all my projects… I love the ability to commit changes when I’m on an airplane or stuck somewhere without internet access. However, I still like to be able to push my git project to a remote server for backup and accessibility, and I’m not going to pay for github. Don’t get me wrong, github is fine for public projects and collaborative development, but for my personal development stuff, it’s an unnecessary expense.

Well, I always forget how to setup a remote master so that I can push and pull and keep a backup on a remote server. Here are my quick notes…. for a detailed explanation see Tim Lucas’s tutorial.

On server:

On local machine:

And you’re all set!