Ok so i think I did everything correctly so far even the SSH commands with the “mongrel” read out. Then when the install instructions say go to http://0.0.0.0:3000/startup in my browser nothing happens. then I tried asking my hosting company they said they don’t deal with the problems of other peoples software and couldn’t help but the guy did manage to mention he thinks of the 0.0.0.0 as meaning an IP address so I tried substituting the zeros with my IP. still nothing. I tried doing what is normally required in programs I’ve installed on servers which is to go to yourdomain/admin/ or something like that but still I could not find a way. Pleas help? I think its almost done and I would really like to see if this will finally be the right software for my projects (non of the others can cut the cake).

any help would be much appreciated guys? its just basic to install things right? Surly someone knows how to install this thing?

you could try to use wget to see if the local tracks server is functioning with

wget 127.0.0.1:3000

it should return a html with the login or signup form

It that works, the next step is configuring bluehost to forward traffic to Tracks. I don’t know about bluehost, but we do have a contributed howto here: http://www.getontracks.org/wiki/Bluehost/

On Bluehost, you do not need to use the server with port 3000.  You just install the software, and follow the instructions at the wiki site mentioned.  You do need to change the following file.

tracks\public\.htaccess

I am calling “tracks” the main directory for all of the Tracks files and subdirectories.  That .htaccess file should contain the following code.

To get recurring entries to work, you need to change the following file.

tracks\app\views\recurring_todos\_recurring_todo_form.erb

Change “format_date(Time.today)” to “format_date(user_time)”.

To get e-mail to work, set up a forwarder to a piped program, such as forwarding .(JavaScript must be enabled to view this email address) to the following program.  Replace “mysite.com” with your own domain name.

|/home/mysite/tracks/script/runner -e production ‘MessageGateway.receive(STDIN.read)’

Again replace “mysite” here with your root path name.

In this case, “tracks@mysite.com” is your target (“To”) address.  Set Tracks preferences to an originating (“From”) address.  You then send e-mail from the address in the preferences to the address that you have now set Bluehost to forward to the runner application.  This will populate your Tracks with a new action.  You can also forward messages as long as they use these same “from” and “to” listings.  For a different Tracks user, you could change either address, but you will always forward to the same runner application.  The “from” address will determine which account is populated with the new action.  If you are using SMS, then you will want this originating address to match the originating address that your SMS system uses.

The following file does not need a specific “subdir” entry.

tracks\config\site.yml

great howto

the change in _recurring_todo_form.erb is a fix for a bug. This bug is fixed in 1.7.1devel and will be released in the upcoming 1.7.1

Hooray!  Thanks.

Also: for outgoing automated e-mail: create a text file called /home/[mysite]/tasks.sh, as follows.

Replace what’s in brackets there.
Set the file’s permissions to 700.
Next, simply set up a cron job that executes the file, ‘/home/[mysite]/tasks.sh’.
The cron job will execute according to the server’s time zone.  To determine the server’s time zone, use a shell or terminal program and execute the unix command ‘date’.  My Bluehost server is on U.S. Mountain Time.

Example of minor upgrade:

Save old /home/[mysite]/tracks/public/.htaccess file.

Restore old /home/[mysite]/tracks/public/.htaccess file.