Browse Source

Added #522 in modified version

pull/517/merge
Armin Ronacher 13 years ago
parent
commit
7b1c8fd15b
  1. 13
      docs/deploying/cgi.rst

13
docs/deploying/cgi.rst

@ -35,12 +35,23 @@ Usually there are two ways to configure the server. Either just copy the
`.cgi` into a `cgi-bin` (and use `mod_rewrite` or something similar to `.cgi` into a `cgi-bin` (and use `mod_rewrite` or something similar to
rewrite the URL) or let the server point to the file directly. rewrite the URL) or let the server point to the file directly.
In Apache for example you can put a like like this into the config: In Apache for example you can put something like this into the config:
.. sourcecode:: apache .. sourcecode:: apache
ScriptAlias /app /path/to/the/application.cgi ScriptAlias /app /path/to/the/application.cgi
On shared webhosting, though, you might not have access to your Apache config.
In this case, a file called `.htaccess`, sitting in the public directory you want
your app to be available, works too but the `ScriptAlias` directive won't
work in that case:
.. sourcecode:: apache
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f # Don't interfere with static files
RewriteRule ^(.*)$ /path/to/the/application.cgi/$1 [L]
For more information consult the documentation of your webserver. For more information consult the documentation of your webserver.
.. _App Engine: http://code.google.com/appengine/ .. _App Engine: http://code.google.com/appengine/

Loading…
Cancel
Save