I’ve discovered Tracks and love it. I’m currently comparing it to What’s Next. Anyway, one of the requirements (or at least hopes) for this to work for me is to be able to seamlessly access my data whether at my desk (I have a dedicated desktop station) or from away (I also have a laptop which may be on the network or vpn’d in from home).
I work at a company developing technology and storing my database (or all of tracks for that matter) on a webhost is just not an option due to the Intellectual Property issues of what will be contained.
Here’s my vision:
- the main computer hosting the server will be my desktop station
—- I can access tracks from either the desktop (http://localhost) or laptop (http://desktop-ip) when it is up
- when the desktop is off or I’m home I can start up the server on my laptop to see tracks
- the database is seamlessly shared between the two
—- the ideal for this would be to keep the database on my allotted network share drive. This seems like it should be very easy to do.
Currently I’ve tried editing database.yml to edit the development environment to look like this:
The folder ‘tracks’ actually only has the folder ‘db’ inside of it.
I get a ‘500 Internal Server Error’ when I do this.
- is it just editing another file?
- do I need to copy more than the db folder to my network share?
Please let me know if any other information would be helpful.