![mod api the forest path user config mod api the forest path user config](https://modapi.survivetheforest.net/uploads/images/2x03wgvuzpe2q4eo0l9v9pcdscpqtds2r2f4g6cq.png)
This can be inconvenient,Įspecially if the web server is a shared resource hosting other webĪpplications at the same time, or you don’t have root access to be able to Server in order for changes to be picked up.
#Mod api the forest path user config code#
When embedded mode is used, whenever you make changes to your WSGIĪpplication code you would generally have to restart the whole Apache web Used to handle normal static file requests. That is, the application will be hosted within the Apache worker processes Note that you obviously should substitute the paths and hostname withīy default any WSGI application will run in what is called embedded mode. ico / usr / local / > Require all granted WSGIScriptAlias / / usr / local / > Require all granted Īfter appropriate changes have been made Apache will need to be restarted.įor this example, the URL ‘ ’ would then be used com DocumentRoot / usr / local / txt Alias / favicon. Other directories and that the only thing in that directory be the WSGIĪpplication script file, and if necessary any support files it requires.Ī complete virtual host configuration for this type of setup would It is thus recommended that a special directory be setup distinct from This case any misconfiguration of Apache could end up exposing your whole That would mean allowing Apache to serve up any files in that account. You also should not use the home directory of a user account, as to do Is because if that directory is otherwise being used as a source of staticįiles, the source code for your application might be able to be downloaded. This case NOT be placed within the existing DocumentRoot for your mainĪpache installation, or the particular site you are setting it up for. Note that it is highly recommended that the WSGI application script file in Order allow, deny Allow from all = 2.4 > Require all granted
![mod api the forest path user config mod api the forest path user config](https://assets2.rockpapershotgun.com/forestheader.jpg)
To do this the Directory directive must be used: Located outside of any directories already configured to be accessible toĪpache, it will be necessary to tell Apache that files within thatĭirectory can be used. Still be applied to indicate who can actually access the WSGI application.īecause the Apache access controls will apply, if the WSGI application is Of reasons, the main one being so that all the Apache access controls can It is not possible to specify anĪpplication by Python module name alone. Note that an absolute pathname must be used for the WSGI application scriptįile supplied as the second argument. The sample WSGI application code should be placed.
![mod api the forest path user config mod api the forest path user config](https://modapi.survivetheforest.net/images/games/game-escapethepacific.jpg)
Pathname to the WSGI application script file. The second argument to the WSGIScriptAlias directive should be an absolute
![mod api the forest path user config mod api the forest path user config](https://modapi.survivetheforest.net/images/tutorial/ilspy.png)
The only exception to this is if the WSGIĪpplication is to be mounted at the root of the web server, in which case For this case the URL should notĬontain a trailing slash. The first argument to the WSGIScriptAlias directive should be the URL It cannot be used withinĮither of the Location, Directory or Files container directives, nor can it The VirtualHost container for a particular site. Theĭirective can be used at server scope but would normally be placed within This directive can only appear in the main Apache configuration files. WSGIScriptAlias / myapp / usr / local / www / wsgi - scripts / myapp.