Hey,
I have just a few observations to report about the new version of Mongrel
(0.3.13) on Win32.
1. When installing a new service, I have to use -N instead of -n to set the
name of my app. The help file (-h option) has this right but the examples
and such on the website all use -n.
2. The website documentation on the Win32 howto lists service::delete as a
command but it should be service::remove
3. When installing my app as a service, I have to point to the \public
directory in order for everything (scripts and stylesheets) to work right:
mongrel_rails service::install -N myapp -r c:\path\to\myapp\public -p
4000
FWIW,
Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/mongrel-users/attachments/20060617/e522dde1/attachment.htm
On 6/17/06, Eric Lund <etlund at gmail.com> wrote:> > > Hey, > > I have just a few observations to report about the new version of Mongrel > (0.3.13) on Win32. > > 1. When installing a new service, I have to use -N instead of -n to set the > name of my app. The help file (-h option) has this right but the examples > and such on the website all use -n. >That, and other new options was discussed past weeks in this list. The -n is now used for "num-processors" option, and clash with the new gem_plugin schema (because service:: should *extend* what mongrel_rails do, not overwrite. We opted for -N, but guess the docs, as usual, never get updated... will work on that now.> 2. The website documentation on the Win32 howto lists service::delete as a > command but it should be service::removePreviously, you installed/uninstalled a mongrel service, but to follow naming conventions, when you install/add, you later remove, not delete. (AFAIK, the same with exit/quit differences between win and mac). I''ll update that when Zed do the commit for the changes he made (the docs mostly, cannot see the new info on my checkout).> > 3. When installing my app as a service, I have to point to the \public > directory in order for everything (scripts and stylesheets) to work right: > > mongrel_rails service::install -N myapp -r c:\path\to\myapp\public -p > 4000 >THAT don''t sound right, ''ll check that out now and see... If you''re registering the service outside your application folder, you sould try to use -c option instead of -r mongrel_rails service::install -N myapp -c c:\path\to\myapp -p 4000 The service chdir to that root and resolve ''public'' inside of it. Let me know if that work for you. Regards,> FWIW, > > Eric > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > >-- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi
On Sat, 2006-06-17 at 16:39 -0600, Eric Lund wrote:> Hey, > > I have just a few observations to report about the new version of > Mongrel (0.3.13) on Win32. > > 1. When installing a new service, I have to use -N instead of -n to > set the name of my app. The help file (-h option) has this right but > the examples and such on the website all use -n. > > 2. The website documentation on the Win32 howto lists service::delete > as a command but it should be service::remove > > 3. When installing my app as a service, I have to point to the \public > directory in order for everything (scripts and stylesheets) to work > right: > > mongrel_rails service::install -N myapp -r c:\path\to\myapp > \public -p 4000Thanks Eric, those changes will be up on the site shortly. Not sure why the public dir is needed though. I''ll look at that. Zed
> If you''re registering the service outside your application > folder, you should try to use -c option instead of -r > > mongrel_rails service::install -N myapp -c c:\path\to\myapp -p 4000 > > The service chdir to that root and resolve ''public'' inside of it. > > Let me know if that work for you. >Cool, thanks for that info. I reinstalled the service with the -c option and the \public was not required (as expected). I tried again using -r, just to make sure, and again I had to add \public to the path to get it all to work. Thanks, Eric
On 6/17/06, Eric Lund <etlund at gmail.com> wrote:> > If you''re registering the service outside your application > > folder, you should try to use -c option instead of -r > > > > mongrel_rails service::install -N myapp -c c:\path\to\myapp -p 4000 > > > > The service chdir to that root and resolve ''public'' inside of it. > > > > Let me know if that work for you. > > > > Cool, thanks for that info. > > I reinstalled the service with the -c option and the \public was not > required (as expected). I tried again using -r, just to make sure, and > again I had to add \public to the path to get it all to work. >-c option is for the chdir that will be made prior starting rails. -r, on the contrary, just point to the docroot (or known as public in rails). Lets say my application is located in c:\myapp\A\ I chdir into it, and create a rails service. the root (-c) used will be ''c:\myapp\A'' and the docroot will be just ''public''. if for some reason I want to serve the static content from a folder named "dummy", I need to pass that to the service install command: (inside c:\myapp\A\) mongrel_rails service::install -N myapp -r dummy Take note I didn''t use the expanded path of dummy, because it is resolved relatively from -c option, which in this case, assume current dir. Sounds weird, and with my poor english worse... but hope I make this clear. Regards, -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi> Thanks, > > Eric > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >