Currently Being ModeratedApr 17, 2012 3:08 AM (in response to Michael Carter)
Unfortunately you might be SOL. Updating Rails will hose your server.
Currently Being ModeratedApr 17, 2012 5:32 AM (in response to Michael Carter)
I'll add this, here's what I would do if I were you. I would dump the PostgreSQL database for the wiki and back it up, rebuild my server from from scratch and then restore the database.
To dump the database for the wiki, run this in terminal:
sudo pg_dump -U _postgres collab -c -f ~/Desktop/collab.sql
The database will be dumped to your desktop, put it in a safe place.
Rebuild your lion server, save hostname and everything. Now, restore the database:
psql -U _postgres -d collab -f ~/Desktop/collab.sql
Currently Being ModeratedApr 17, 2012 10:08 AM (in response to Jonathan Melville)
Well isn't that wonderful. I wish I would have seen that article before installing the useless log reader.
Anyone know if there is a way to back out from this sort of change (re-install the components of wikid) without having to re-install everything from scratch?
Currently Being ModeratedApr 17, 2012 11:54 AM (in response to Michael Carter)
Okay, this is solved.
I reverted the version of the 'rack' rubygem to 1.2.1 (it had been upgraded to 1.4.1 for the ruby app I installed).
Once I removed the other versions of 'rack' and installed version 1.2.1, the wiki began working again.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points