incubator-bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Martin <gary.mar...@wandisco.com>
Subject Re: [Apache Bloodhound] BloodhoundInstall modified
Date Tue, 10 Jul 2012 09:53:45 GMT
Well, for the sake of anyone thinking that it would only be useful if 
they were to set up CI, at the moment it would be good for some people 
to try it out on whatever they like.

If you are happy to install virtualenv and pip to your system (sticking 
to sqlite rather than a postgresql db and ignoring instructions to set 
up the webserver), it should otherwise be possible to install bloodhound 
as a non-privileged user for testing.

Cheers,
     Gary


On 07/10/2012 03:59 AM, Olemis Lang wrote:
> Jenkins + anything else I can connect to it (lots of plugins indeed ,
> Selenium et al. included ;) . But if not exactly Selenium tests then
> we could think about twill , or even about running Trac test suite to
> see how our patches behave (i.e. detect any regression in Trac copy @
> trunk with respect to vendor branch ;) .
>
> Nonetheless , I'd really appreciate if somebody else could volunteer
> too , considering the fact that I'm a little bit involved in
> programming as well ... ;)
>
> On 7/9/12, Gary Martin <gary.martin@wandisco.com> wrote:
>> Olemis,
>>
>> Excellent.. thanks for volunteering!
>>
>> I suppose that it depends on how your CI works. The bare minimum to
>> decide that an instance is working is to hit a page and get no system
>> errors. Are you after selenium tests to make your CI work here?
>>
>> Cheers,
>>       Gary
>>
>>
>> On 09/07/12 17:19, Olemis Lang wrote:
>>> ok I'll try it in a while in some CI server . What would you suggest
>>> me to do in order to know (<= or at least have a idea) whether install
>>> was successful and everything is working ok ?
>>>
>>> On 7/9/12, Gary Martin <gary.martin@wandisco.com> wrote:
>>>> Hi,
>>>>
>>>> I just updated the
>>>> https://issues.apache.org/bloodhound/wiki/BloodhoundInstall page to
>>>> document using bloodhound_setup.py instead of installer.py
>>>>
>>>> If anyone can check it through, that would be great.
>>>>
>>>> Cheers,
>>>>        Gary
>>>>
>>>>
>>>> On 07/09/2012 12:48 PM, Apache Bloodhound wrote:
>>>>> Page "BloodhoundInstall" was changed by gjm
>>>>> Diff URL:
>>>>> <https://issues.apache.org/bloodhound/wiki/BloodhoundInstall?action=diff&version=6>
>>>>> Revision 6
>>>>> Changes:
>>>>> -------8<------8<------8<------8<------8<------8<------8<------8<--------
>>>>> Index: BloodhoundInstall
>>>>> =========================================================================
>>>>> --- BloodhoundInstall (version: 5)
>>>>> +++ BloodhoundInstall (version: 6)
>>>>> @@ -10,7 +10,6 @@
>>>>>      {{{
>>>>>        sudo apt-get install python python-setuptools python-pip
>>>>>      }}}
>>>>> -
>>>>>
>>>>>     At the moment it is also recommended that you install virtualenv
>>>>> with
>>>>> either
>>>>>      {{{
>>>>> @@ -79,36 +78,45 @@
>>>>>
>>>>>     To continue the installation, refer to
>>>>> BloodhoundDetailedInstallation
>>>>> before continuing to the Testing the Server section below.
>>>>>
>>>>> -== Installation Script ==
>>>>> +== Installation ==
>>>>>
>>>>> -Bloodhound provides a simple installation script that is capable
>>>>> installing a basic Bloodhound setup based on the answers to a few
>>>>> questions. If you have Subversion installed, this is how you can try
it
>>>>> out:
>>>>> +To install Bloodhound, the following steps represent the current
>>>>> recommended method:
>>>>> +
>>>>>      {{{
>>>>> -   svn co
>>>>> https://svn.apache.org/repos/asf/incubator/bloodhound/trunk/installer/
>>>>> -   cd installer
>>>>> -   python installer.py
>>>>> +   svn co https://svn.apache.org/repos/asf/incubator/bloodhound/trunk
>>>>> bloodhound
>>>>> +   cd bloodhound/installer
>>>>> +   virtualenv bloodhound
>>>>> +   source ./bloodhound/bin/activate
>>>>> +   pip install -r requirements-dev.txt
>>>>> +   python bloodhound_setup.py
>>>>>      }}}
>>>>>
>>>>>     and answer the questions based on whether you chose to use SQLite
or
>>>>> PostgreSQL. If you choose an SQLite installation, you should only have
>>>>> to
>>>>> specify a username and password to login to Bloodhound with once it is
>>>>> running. For PostgreSQL, the only extra questions will be to specify
>>>>> the
>>>>> database name, database user and the associated password.
>>>>>
>>>>>     In fact it is possible to specify all these details on the command
>>>>> line
>>>>> which also allows you to set additional options like the host for the
>>>>> PostgreSQL database and provide a different location for the
>>>>> installation.
>>>>> For more information on these options, run
>>>>>      {{{
>>>>> -   python installer.py --help
>>>>> +   python bloodhound_setup.py --help
>>>>>      }}}
>>>>>
>>>>> +Note that for windows, amongst the other differences you should use
>>>>> + {{{
>>>>> +   bloodhound\bin\activate.bat
>>>>> + }}}
>>>>> +to activate the bloodhound environment.
>>>>> +
>>>>>     == Testing the Server ==
>>>>> -On linux and other unix-like systems you can then run bloodhound
>>>>> using::
>>>>> +
>>>>> +If the bloodhound_setup.py script completed successfully, you will be
>>>>> informed of the appropriate command to run the test server and the
>>>>> appropriate url to check. If you did not set any advanced options, you
>>>>> should find that you can start bloodhound using:
>>>>>      {{{
>>>>> -   source ./bloodhound/bin/activate
>>>>>        tracd ./bloodhound/environments/main --port=8000
>>>>>      }}}
>>>>>
>>>>> -On windows you should instead use:
>>>>> +and you will be able to access Bloodhound on
>>>>>      {{{
>>>>> -   bloodhound\bin\activate.bat
>>>>> -   tracd bloodhound\environments\main --port-8000
>>>>> +   http://localhost:8000/main/
>>>>>      }}}
>>>>>
>>>>> -At this point you should be able to access Bloodhound on
>>>>> http://localhost:8000/main/ and you can login with the admin user and
>>>>> password details you supplied earlier.
>>>>> +Remember that if you run tracd from a fresh shell, you will need to
>>>>> activate the virtual environment first and you should ensure that the
>>>>> path
>>>>> to the directory containing the environment is correct. An incorrect
>>>>> path
>>>>> to the environment will result in an "Environment not found" message,
>>>>> as
>>>>> will specifying the wrong environment name in the url.
>>>>>
>>>>>     == Web Server ==
>>>>>
>>>>> @@ -147,7 +155,7 @@
>>>>>           AuthType Digest
>>>>>           AuthName "Bloodhound"
>>>>>           AuthDigestDomain /bloodhound
>>>>> -      AuthUserFile
>>>>> /path/to/bloodhound/environments/bloodhound.htdigest
>>>>> +      AuthUserFile
>>>>> /path/to/bloodhound/environments/main/bloodhound.htdigest
>>>>>           Require valid-user
>>>>>         </LocationMatch>
>>>>>       </VirtualHost>
>>>>> -------8<------8<------8<------8<------8<------8<------8<------8<--------
>>>>>
>>>>> --
>>>>> Page URL: <https://issues.apache.org/bloodhound/wiki/BloodhoundInstall>
>>>>> Apache Bloodhound <https://issues.apache.org/bloodhound/>
>>>>> The Apache Bloodhound (incubating) issue tracker
>>>>>
>>>>> This is an automated message. Someone added your email address to be
>>>>> notified of changes on 'BloodhoundInstall' page.
>>>>> If it was not you, please report to .
>>>>
>>
>> --
>> Gary Martin
>> gary.martin@wandisco.com
>> gjm@apache.org
>>
>>
>



Mime
View raw message