My favorites | Sign in
Project Home Downloads Wiki Issues Source
Search
for
Downloads  
Downloading and installing Taskr
Phase-Deploy
Updated Feb 4, 2010 by matt.zuk...@gmail.com

You can download the Taskr RubyGem package or source code directly from the Taskr RubyForge downloads page.

However, the preferred method is to install via the central RubyGems repository, since this will automatically grab the required dependencies for you.

Installing via RubyGems

  1. Make sure that you have a Ruby interpreter installed. Version 1.8.6 or later is recommended. If you're on Windows, the quick and easy way to install Ruby is the One-Click Installer.
  2. You will also need the RubyGems package management system. Generally this is automatically installed for you along with the Ruby interpreter. To see if you have RubyGems installed, open up a command prompt and type gem. If that doesn't work, you will need to install it manually.
  3. Once RubyGems is installed, you should be able to isntall Taskr by running the command: gem install taskr
  4. Answer 'Yes' when asked about installing dependencies.

Taskr should now be installed. Try running taskr from your command line. Taskr needs to write some configuration files to /etc and by default it writes its logs to /var/log/taskr.log, so you will have to run the taskr command as root (i.e. sudo taskr). Try taskr -h if you need to store your configuration files elsewhere.

The first time you run it, Taskr will try to create a default configuration file for you in /etc/taskr/config.yml and it will then exit. Have a look inside this file and edit it to your needs. Taskr requires a SQL database, and configuration examples are provided for various database servers (MySQL, PostgreSQL, SQLite, etc.). Before running the taskr command again, make sure that the database you've configured is ready to be used. For example, if you're using mysql, you'll have to create the database first:

mysqladmin -u root -p create taskr

Once you've configured everything and granted access to the database, run taskr again. It should start up this time and run in the foreground.

You can also use taskr-ctl start to start the server in the background. Also see HowToInstallAsaService.

Once it's up and running, your Taskr server should be accessible at http://localhost:7007/tasks (although this may differ if you've changed your configuration).

Have a look at at the BuiltInActionTypes page for some info on how to schedule a new job.

Installing Manually

The RubyGem method describe above is preferred, but if you insist...

  1. Make sure you have a Ruby interpreter installed. Version 1.8.6 or later is recommended.
  2. Download the dependencies. You will need (at least):
  3. Install the dependencies as per their individual install instructions. If for some insane reason you're trying to avoid RubyGems, the general procedure is to install the libraries somewhere in Ruby's include path (for example /usr/lib/ruby/site_ruby/1.8 on some Linux systems).
  4. Download the Taskr source archive from Taskr RubyForge downloads page.
  5. Untar it and cd into the uncompressed directory.
  6. Run ruby setup.rb.

Taskr should now be installed. See the postamble in the Installing via RubyGems section above for further instructions.

Obtaining the Source Code

Taskr is written in a interpreted language (Ruby), so there really isn't a difference between the runable distribution and the "source code" (i.e. the RubyGem and tar packages include all of the source code).

However, if you want to grab a copy of the latest development source code, have a look at Taskr's Subversion repository.

Comment by art...@gmail.com, Jan 23, 2008

Is it possible to have config file in some other place than /etc/taskr/config.yml? I have several applications on my server and would like to have separate taskr instances running regular maintenance tasks on them.

Comment by Rotom...@gmail.com, Oct 9, 2008

Just downloaded and installed taskr. Getting error message: rubygems.rb:139:in `activate': can't activate activesupport (= 2.1.0), already activated activesupport-2.1.1] (Gem::Exception)

How can I fix that?

Thanks.

Comment by Rotom...@gmail.com, Oct 11, 2008

I have updated the 'rails' gem and the problem is now gone.


Sign in to add a comment
Powered by Google Project Hosting