> 1. Did you install Radiant from source or use the gem? > Gem > 2. If you installed Radiant using the gem, did you use the --unpack flag > with the radiant command? > Yes -- Dreamhost's ruby server ATM on 2 servers (Confirmed now) does not respond well to custom-installed gems. I had to unpack radiant and then had to toss radius into the vendor/ folder to make work properly on dreamhost. Any suggestions how to correct before I release my tutorial on how to get the web server's engine to recognize the personal installation of gem? Yes, I made .bash_profile and source'd it. Also made .gemrc. Restarted dispatch.fcgi (Currently running) and won't pick up these two gems (Others work) -- Yes, I did chmod those as well. > 3. Would you mind if we dropped support for upgrading unpacked Radiant > applications (apps installed using the --unpack flag) if it > means that Radiant releases can occur more frequently? > I would mind for now just because dreamhost's gem is goofed. Will work more on it this weekend to try to make it work to maybe make a better 'Install your own gems on DreamHost' tutorial as well. If I could make it work, I have no problems. :)
_______________________________________________ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
