On 29 February 2016 at 01:53, Sam Ruby <[email protected]> wrote:
> On Sun, Feb 28, 2016 at 8:28 PM, sebb <[email protected]> wrote:
>> 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:
>>>>
>>>> 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
>
> I'm clearly not getting that. Note that I access my copy of whimsy as
> http://localhost/whimsy, so I would access the roster application as
> http://localhost/whimsy/roster.
>
> If you are trying to 'mount' the roster application at the root of
> your webserver, your setup would look something like this:
>
I'm using virtual hosts for different apps (projects, reports, etc) so
I guess this is closer to what I need.
> Alias /roster/ /srv/whimsy/www/roster/committer
> <Location /roster>
> PassengerBaseURI /roster
> PassengerAppRoot /srv/whimsy/www/roster/committer
> PassengerAppEnv development
> Options -Multiviews
> </Location>
Doesn't work.
However this does:
Alias /roster/ /srv/whimsy/www/roster
<Location /roster>
PassengerBaseURI /roster
PassengerAppRoot /srv/whimsy/www/roster
PassengerAppEnv development
Options -Multiviews
</Location>
Yay!
> Should that not work... have you ever run Docker or Vagrant before? I
I have got Docker; don't think I have used Vagrant.
> probably can quickly set up one or the other. My thoughts are that
> once you have a working system that you can compare against, spotting
> the difference with your current setup would be much easier. And that
> could lead to updates to the documentation to help others.
I think it would help to document what the paths represent, and for
file paths, what one would expect to find there.
e.g. I assume PassengerAppRoot is a local path, and need to point to a
rake app, i.e. a whimsy directory containing config.ru.
This should make it easier to check the settings are correct.
> - Sam Ruby
