On 29 February 2016 at 01:04, Sam Ruby <[email protected]> wrote: > On Sun, Feb 28, 2016 at 7:41 PM, sebb <[email protected]> wrote: >> On 29 February 2016 at 00:17, Sam Ruby <[email protected]> wrote: >>> On Sun, Feb 28, 2016 at 4:56 PM, sebb <[email protected]> wrote: >>>> On 28 February 2016 at 21:28, Sam Ruby <[email protected]> wrote: >>>>> So you went straight for the advanced instructions. Cool. >>>>> >>>>> Did you try rake server? >>>> >>>> No. >>>> >>>> I did not understand what constituted a Rack application. >>>> But I see that www/roster has a Rakefile so I have just tried >>>> >>>> cd /www/roster >>>> rake server >>>> >>>> and I can now see the roster index and can use the committers page >>> >>> Sweet! >>> >>>>> Which index page are you referring to? The problem looks to be one that >>>>> can be solved be the use of relative URLs. If you tell me which index >>>>> page, I'll take a look when I get back home. >>>> >>>> The main one, i.e. whimsy.apache.org >>> >>> Now I understand. Should you ever want to set up the whole site to >>> run under Apache httpd, you would need to follow the instructions to >>> configure the rack applications (now that you know how to identify >>> them) using Phusion Passenger. >> >> I thought I *had* configured www/roster; see my posting from 21:07 >> (else-thread) >> >> How should I have done it? > > I went back and looked closer. You configured www/roster/committer, > not www/roster. Here's my config: > > <Location /whimsy/roster> > PassengerBaseURI /whimsy/roster > PassengerAppRoot /var/whimsy/www/roster > PassengerAppEnv development > Options -Multiviews > # CheckSpelling Off > </Location> > > Alias /whimsy/roster/ /var/whimsy/www/roster
Still does not work. I get The requested URL /roster/committee/ was not found on this server. The requested URL /roster/committer/ was not found on this server. For http://my.whimsy/roster/ I get a directory listing of www/roster >>> Meanwhile, running individual >>> applications when you need them is much easier. >> >> So why would one need to set up the whole site for development? > > I actually had not done that myself until I wrote up the instructions. > Now I've found I like it. > > If you are working primarily on one tool, or even only expect to work > on one tool at a time, then starting and stopping that tool as needed > is easy and requires little setup. > > As somebody who might be working on one tool and want to put that work > aside for a moment when a bug report comes in on another tool, having > all of the tools ready to be spun up at will by simply visiting the > URL is handy. A few days ago, Brett reported a bug in the board > agenda tool, so I went to my local copy, saw the problem there, made a > fix, saw it worked, committed and pushed it. All without worrying > about whether or not I had another server using port 3000. > > [snip] > >>>>>> The requested URL /roster/committer/ was not found on this server. >>>>>> >>>>>> I added what I thought was the correct config and restarted Apache: >>>>>> >>>>>> Alias /whimsy/roster/committer/ /srv/whimsy/www/roster/committer >>>>>> <Location /whimsy/roster/committer> >>>>>> PassengerBaseURI /whimsy/roster/committer >>>>>> PassengerAppRoot /srv/whimsy/www/roster/committer >>>>>> PassengerAppEnv development >>>>>> Options -Multiviews >>>>>> </Location> > > Note the inclusion of /committer in the AppRoot. The smallest > possible Rack application contains two directories and one file: > > https://github.com/apache/whimsy/tree/master/www/racktest > > - Sam Ruby
