Publishing ‘Tasks’ in Evolution.
Well. .. why would anyone want to publish their tasks?
- You are working in team and you want everybody to know what you r doing.
- Status reports ?
Anyway here goes …
Your Evolution tasks are stored in ICAL format under $HOME/.evolution/tasks/local/
The default task list will be under $HOME/.evolution/tasks/local/system/task.ics
If you have more than one task list then you’ll find something like this.. .
I’m not sure why they have been named like this.. You need to find which tasks.ics = task list.
Thatz all we want to know.. Now itz time for writing some scripts to copy tasks.ics to your webserver. I want to publish this on a machine that runs 24/7. So we need to SCP this task.ics to the server. this can be done by a simple one line script and putit as a cronjob for syncing the changes automtically. something like
scp /home/jjohnny/.evolution/tasks/local/1155787868.6980.0@helios/tasks.ics firstname.lastname@example.org:~/public_html/
As you can see SCP is very simple to use. But it prompts for a password everytime you copy the file. Not good. This can be overriden by createing a ssh-key. Herez how to do it :
- Create a local ssh-key by using “ssh-keygen”. It’ll ask for passphrase (u could ignore it). Once the keys are generated you’ll have a public key and a private key. Public key will be in $HOME/.ssh/id_rsa.pub
- Copy id_rsa.pub to the server. “scp $HOME/.ssh/id_rsa.pub myuser@myserver:~/
- Now log into ur server : “ssh -X myser@myserver”
- You should be able to find the public key (id_rsa.pub).
- Now “cat id_rsa.pub ~/.ssh/authorized_keys”
Once that done you dont have to enter your password when u scp/ssh to the server. Now letz put the ‘one line’ script on a cronjob every five minutes. Now you evolution tasks are published and your team always updated.
Note : You may have to improve the script based on your needs. If your network is not reachable , cron will send a mail
to you complaining.