Julian, It refuses to start when the group can write. It starts okay when i remove write permission from the groups.
Interestingly, when i generate a flat or very_flat framewok, it doesn't care about the permissions or the dependencies. I think I'd rather start out lean and add what I need rather installing it all and trying to cut away the fat. Overall, I think merb will be worth exploring. I just had to express my astonishment at the messages I was initially greeted with. Philip, Where did you get the idea I was using windows? I left years ago to escape DLL-hell. glenn On Feb 4, 9:11 pm, Julian Leviston <[email protected]> wrote: > I agree - the explicit dependencies and not installing thing is a pain > in the arse. Explicit is better because you make 100% sure when it > runs it will run properly, but not installing the required stack is > crazy. > > The merb error messge you're complaining about is not that it's > insecure, it's that it needs to write to folders that it can't. Bad > error message. But, if you've been devving with rails for so long, you > really should know this man. Permissions. > > Blog:http://random8.zenunit.com/ > Learn rails:http://sensei.zenunit.com/ > > On 05/02/2009, at 1:02 PM, "[email protected]" > <[email protected] > > > wrote: > > > I've been developing with rails for a couple of years and I'm finally > > getting around to trying merb for the first time. The instructions on > > the home page seemed simple enough, but I've run into a couple of > > problems before even seeing the welcome page. > > > The first time i tried running merb, I got > > > Loading init file from /Users/pcf/prac/merb/my_application/config/ > > init.rb > > Loading /Users/pcf/prac/merb/my_application/config/environments/ > > development.rb > > /Users/prec is insecure (40730). It may not be group or world > > writable. Exiting. > > > After figuring out that 'may not be' meant 'can not be' and not 'might > > not be', I removed group write permission from the directory and tried > > again. This time I got. > > > ~ FATAL: The gem data_objects (= 0.9.10.1, runtime), [] was not > > found > > > I apparently had version 0.9.10.1. I installed the required version > > and was rewarded with > > > ~ FATAL: The gem do_sqlite3 (= 0.9.10.1, runtime), [] was not > > found > > > I managed to find dependencies.rb before totally losing my sanity, and > > I changed dm_gems_version and do_gems_version to ">=0.9.10.1" so I can > > finally see the fresh merb app screen, but I'm left with a couple of > > questions before I go too much farther: > > > 1) Why does merb REFUSE to run in a DEVELOPMENT environment if it > > deems my home directory 'insecure', and what other directories or > > resources is it going to monitor for me? > > > 2) What's with the dependencies? Are things likely to break because I > > changed = to >= ? Am I going to have to drag around a vendor > > directory with all verions of all pages or make sure the gems on all > > machines have every version of every gem? Or if I get around to RTFM- > > ing will I find out there's some cool built-in solution? > > > thanks, > > glenn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
