Re: EXT: Looking for documention on deploying roundup with mod_wsgi

Hi Garth:

In message
<BN6P101MB024252A8C4211DB40DEBEC65E89A0@BN6P101MB0242.NAMP101.PROD.O
UTLOOK.COM>, "Jensen, Garth (SolarDevelopment Non-GE)" writes:
>By the way, I found the instructions for using mod_wsgi-express on
>the mod_wsgi pypi page (https://pypi.org/project/mod-wsgi/) pretty
>straight forward.  In fact, the Getting Started section of the full
>mod_wsgi documentation on readthedocs says, "For a simpler way of
>running a Python WSGI application using mod_wsgi, also checkout
>mod_wsgi-express, details of which can currently be found at: [the
>pypi page]" You might be able to save having to explain a lot of
>details by reference that page.

I have both references at the top of the section.

>Thanks for your work on this.  I've been enjoying working with Roundup.

I am glad you are enjoying it and finding it useful. We can always use
the help.

>> -----Original Message-----
>> [...]
>> I assume the web interface tested out ok. Have you tried the rest interface
>> under wsgi? We had a report that it had issues under wsgi. See:
>> https://issues.roundup-tracker.org/issue2551047.
>
>The web interface is working great.  I had no idea there was a REST
>API for roundup.  I can't find any mention of it in the Docs.  If you
>can direct me to some info about it, I can give a try testing it.

I sent a quick reply about this in private email. Garth is running
1.6.1. This doesn't have the rest interface which is only available
from the current development release until 2.0.0.alpha starts getting
released.

>> Also Thomas mentioned that you can install mod_wsgi using:
>> 
>>   sudo apt install apache2 libapache2-mod-wsgi
>> 
>> You document using the pip method. Is there some reason you went the pip
>> route rather then the packaged mod_wsgi? Was use of mod_wsgi-express to
>> make an apache config part of your decision?
>
>I did find the option to ` sudo apt install apache2
>libapache2-mod-wsgi`, but I was worried it might not give me
>mod_wsgi-express and I believe I ran across warnings that some
>precompiled mod_wsgi packages were very out of date.  I have no idea
>if either of those fears were justified, but pip seemed super easy
>and guaranteed to work.  I'm a total Apache neophyte and liked the
>idea of not having to climb up the Apache configuration learning
>curve.

Fair enough. Configuring apache can be a bear.

>> Also are you using release 1.6.1 or the current development head?
>
>The stable 1.6.1 release.

>> Also in your docs you say:
>> 
>>     you'll need to configure a UNIX group with appropriate privileges
>>     as described elsewhere in the Roundup docs.
>> 
>> do you mean the UNIX Environment Steps section of installation.txt?
>
>Yes, exactly.

Reference added.

>> Also did you configure systemctl to start the server at port 80, or
>> do you have to login to run sudo /etc/mod_wsgi-express-80/apachectl
>> start?
>
>Not sure I understand the question.  I believe the command
> "mod_wsgi-express setup-server wsgi.py --port=80 --user www-data
>    --group www-data --server-root=/etc/mod_wsgi-express-80" creates the
>directory at /etc/mod/_wsgi-express-80 with all the required
>configuration files in it.  I didn't have to do any other
>configuration.

In your notes after you run the command above you run:

  sudo /etc/mod_wsgi-express-80/apachectl start

usually you would run sudo systemctl start apache (or maybe httpd)
to have the init process start the server the same way it would get
started if the system was just booted.

So does apache start with wsgi and roundup if you simply (re)boot the
system?

>> In that section, I am not sure how to interpret:
>> 
>>   To test the above you should create a demo tracker with
>>   ``python demo.py``. Edit the ``config.ini`` to change the web
>>   URL to "http://localhost:8917/".
>> 
>> Was that something else you considered misleading?
>
>Yes.  Creating a tracker with "python demo.py" made no sense to me.

Agreed I think they were using that as a replacement for roundup-admin
init but....

>Also the code sample provided may have worked in a specific scenario
>with an older mod_wsgi, but the comments I found elsewhere pointed
>out:
>(1) tracker_home should be an absolute path 
>(2) mod_wsgi looks for the name "application" not "app"
>(3) the last two lines shouldn't be needed.

Yup, I have had the same reports, but I didn't have the time to test
and verify a working setup.

Thanks for your feedback. Have a great day.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.