bloodhound-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Ollos <ryan.ol...@wandisco.com>
Subject Re: Running Bloodhound via apache: 404
Date Tue, 17 Sep 2013 21:36:54 GMT
On Tue, Sep 17, 2013 at 2:31 PM, Jared Duncan <j@jdunk.com> wrote:

> Thanks so much for that Ryan; very elucidating.
>
> Yeah, I wasn't sure where that line was exactly between the source/setup
> files and the files needed in the end once installation is complete, let
> alone that there are actually a good 4 separable components here as you've
> pointed out.  I did at first try moving the
> bloodhound/installer/bloodhound/ and/or
> bloodhound/installer/bloodhound/site/ dirs to a higher level elsewhere
> and that resulted in something very much broken.  I probably needed to pass
> the dir path as an argument to one of the install steps instead of moving
> it after the fact.  It's unclear in the installation steps that in a few
> cases, "bloodhound" refers to an actual directory name/path that is then
> created, and not an argument/flag to differentiate it from vanilla trac,
> for example.
>
> Then, bloodhound-src can be deleted after install, and a newer version can
>> be extracted to that location when upgrading. Static resources are deployed
>> to www, and we can document the necessary permissions for each of these
>> directories in a simple way. I'll have to try it out to be sure, but I
>> think the webserver user will only need r-access to python-virtualenv and
>> www, and will need w-access to bloodhound-env.
>>
>
> This!  That would be so much clearer and, imo, would be a better way to
> instruct installation not only because of the permission and updateabilty
> reasons you mentioned but also to significantly reduce the learning curve
> and confusion for new users / improve adoption.  Although I'm not yet
> familiar with what params to which commands drive to output to one
> directory or another, I'm going to go ahead and try to arrive at exactly
> this setup right now and I'll test it out and let you know.  :)
>
> To be clear, the /srv/site-name/www directory would be the one created by
> "trac-admin deploy", i.e. the command would then be:
>
> trac-admin /srv/site-name/bloodhound-env/main/ deploy /srv/site-name/www
>
> , correct?
>

Yeah, that is correct. Thanks for experimenting and reporting your
feedback. I'll do some experimenting in parallel and it would be great if
we can improve the docs as a result over the next few days.

Mime
View raw message