Wonderful new Tobias, I'm glad I could help. Cheers, Alexei
Director of Web Development - Farallon Geographics, Inc. - 971.227.3173 On Mon, Dec 16, 2013 at 4:01 AM, Tobias Kohr <[email protected]> wrote: > Hi Alexei, > > thank you very much for your help on building, wsgi and virtualenvs! > Following your instructions Arches now runs like a charm on our apache > webserver. > > I will post another question regarding the build scripts in a new thread. > > Best, > Tobias > > > On Friday, December 13, 2013 10:27:31 PM UTC+1, Alexei Peters wrote: > >> Hi Tobias, >> I'm guessing that running "build_full_db_dev.sh" fixed your problem >> because you decided not to run the last "optional" step in the install >> process, which is fine. Unfortunately, those docs fail to mention that if >> you don't run the last step you need to run build/build.sh instead (which >> happens to be included in build_full_db_dev.sh and which is why running >> that fixed your javascript problem). >> >> The proper way to install Arches would be run the following commands: >> 1. Install/install(.bat/.sh) >> 2. Build/build_core_arches(.bat/.sh) >> 3. runserver(.bat/.sh) >> 4. db/ETL/CDS Package/install_package(.bat/.sh) >> 5. db/ETL/CDS Package/load_concepts(.bat/.sh) >> 6. db/ETL/CDS Package/load_test_data(.bat/.sh) <-- if you don't run >> this step then you need to run build/build(.bat/.sh) >> >> >> >> As far as running Arches in production goes, I would recommend that you >> run Arches within virtualenv. Running it within virtualenv insulates your >> application from other packages installed in the global site-packages >> folder or other applications that require differing versions of the same >> package. See https://pypi.python.org/pypi/virtualenv for more info. >> >> If you have Apache installed then you'll need to modify the httpd.conf: >> >> LoadModule wsgi_module modules/mod_wsgi.so <-- make sure this line is >> uncommented >> >> >> You can add the following lines directly after the above LoadModule >> command: >> >> WSGIScriptAlias /{*virtual directory name*} {*full path to arches root >> folder*}/wsgi.py >> WSGIPythonPath "{*full path to arches root folder*}/virtualenv/ENV/lib/ >> site-packages" >> >> <Directory {*full path to arches root folder*}> >> Order deny,allow >> Allow from all >> </Directory> >> >> So for example, if you're project was located at /usr/local/ArchesWeb and >> you wanted to host the site at "MyArches" then the above lines would look >> like this: >> >> WSGIScriptAlias /MyArches /usr/local/ArchesWeb/wsgi.py >> WSGIPythonPath "/usr/local/ArchesWeb/virtualenv/ENV/lib/site-packages" >> >> <Directory /usr/local/ArchesWeb> >> Order deny,allow >> Allow from all >> </Directory> >> >> You would end up accessing the site at http://localhost/MyArches/Arches/ >> >> Hope this helps! >> Cheers, >> Alexei >> >> >> >> >> >> >> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173 >> >> >> On Mon, Dec 9, 2013 at 2:21 AM, <[email protected]> wrote: >> >>> Dear list, >>> >>> we are trying to set up Arches on our server. This has worked quite fine >>> following the Installation Guide. >>> We just needed two additional steps that weren't mentioned (Is it meant >>> to be done this way?): >>> - On page 22 we ran build_full_db_dev.sh additional to >>> build_core_arches.sh to solve Javascript problems >>> - We added a line "python manage.py runserver 0.0.0.0:8000" to >>> runserver.sh to be able to access Arches from another client computer >>> >>> Now we have Arches up and running on the development server. But how is >>> Arches meant to be run in a production environment (like apache webserver)? >>> We have seen the wsgi.py file in the ArchesWeb directory and assumed this >>> <https://docs.djangoproject.com/en/1.2/howto/deployment/modwsgi/>is the >>> way to do it. >>> So we have installed apache2 and mod_wsgi. Figuring that python and >>> django are only installed in our virtualenv, we also added these on the >>> server. >>> However we now still get errors that modules like psycopg2 cannot be >>> found. >>> >>> Is there a list of modules and libraries that needs to be installed on >>> the server to run Arches outside the virtualenv? >>> Or are we totally on the wrong track in order to run Arches on apache? >>> Any help would be greatly appreciated! >>> >>> Best, >>> Tobias >>> >>> -- >>> -- To post, send email to [email protected]. To unsubscribe, >>> send email to [email protected]. For more information, >>> visit https://groups.google.com/d/forum/archesproject?hl=en >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Arches Project" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- > -- To post, send email to [email protected]. To unsubscribe, > send email to [email protected]. For more > information, visit https://groups.google.com/d/forum/archesproject?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Arches Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
