I'm trying to set up a machine using the tarball, so that the guys in our IT department can decide if to go with this solution. I think I managed setting up everything correctly, but I can't access the site even on the localhost. First of all I wanted to check, do I need to run apache, or does the server do that (by running ./script/server)? Because when I tried running apache first, I got an error when trying to run either push_server or ferret_server (I can't remember which one it was),I suppose that's because 443 is taken then. But the only reason I'd run apache is for cit, so if it's needed, how do I change the conf so it doesn't open port 443 (allowing it for cit)? Also the last 3 instructions in the README, am I supposed to run these commands with & at the end? Because when I don't it won't stop running, and I can't access the command line. (Sorry this might have been a silly question but I don't know exactly what & does I just knows it allows me to access the next line on command line) Also in the readme you set RAILS_ENV to production, but in the first step I created a database named cit_dev is this wrong? (I found that I didn't have permissions for cit_dev in step 7 rake db:schema:load, because we only gave permissions to cit.* in step 2 so by changing step 2 to read cit_dev.* it worked.
I suppose you can see that I'm a bit new at this. I'm really excited about your product, and here at work we use some custom made php form which stinks. They're now in the process of evaluating other possibilities, so I'm trying to push this one forward (although we'll have to work on a hebrew translation), instead of going for a pricey closed source system.
You don't really need to run apache, unless you have some other php (or whatever) solutions that need to run off the same server. You can just as well just run ./script/server on port 3000 for example, and access ClockingIT through there. If port 443 is unavailable, change all occurances of 443 to something else in config/juggernaut_config.yml
Running the different servers in the background is left as an exercise for the user. :-) I usually just start up an instance of 'screen' and have each program running in a console in there. I can then detach and re-attach to the screen session from whatever machine I use to log into the server and when I log out everything is left running.
You might want to grab the Darcs version instead of the tgz download from http://wiki.clockingit.com/wiki:source as that has an updated README where the database is correct. You don't really need both a development, testing and production database when you're just running ClockingIT on a server, so all three can point to the same database in config/database.yml.
Another question on running ./script/runner I get the following 2 error lines:
Route segment ":controller" cannot be optional because it precedes a required segment. This segment will be required. Route segment ":controller" cannot be optional because it precedes a required segment. This segment will be required.
