Skip to content

Commit 9d4d5c6

Browse files
committed
add guidance onchoosing web deployment method
1 parent dcef629 commit 9d4d5c6

File tree

1 file changed

+22
-1
lines changed

1 file changed

+22
-1
lines changed

doc/installation.txt

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -631,7 +631,28 @@ privileges to create databases.
631631
Configure a Web Interface
632632
-------------------------
633633

634-
There are multiple web interfaces to choose from:
634+
There are multiple ways to deploy the web interface. If your
635+
tracker will be heavily used and accessible from the internet, we
636+
suggest using Apache or Nginx in WSGI mode or as a reverse proxy
637+
to the stand alone web server or WSGI server like gunicorn.
638+
639+
A FastCGI deployment with an alternate web server is suitable for
640+
lower traffic sites.
641+
642+
If you already run Zope, Roundup should deploy nicely in that
643+
framework.
644+
645+
If you are internet accessible, but expect a few users, or are on
646+
a hosted web server, using cgi-bin is a reasonable deployment.
647+
648+
Using a true HTTP server provide tools including: DOS prevention,
649+
throttling, web application firewalls etc. that are worth having
650+
in an internet facing application.
651+
652+
If you are running on an internal intranet, you can use the
653+
stand alone server: roundup-server, but even in this environment,
654+
using a real web server to serve static files and other resources
655+
will perform better.
635656

636657
.. contents::
637658
:depth: 1

0 commit comments

Comments
 (0)