http: Add static file support
Static files are configured using a handful of config values. Static files can be handled remotely or locally for prod or dev environments, respectively. Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
This commit is contained in:
25
example.env
25
example.env
@@ -7,9 +7,32 @@
|
||||
# Sqlite3 database path. Defaults to "bans.db"
|
||||
#DB_SQLITE3_PATH=bans.db
|
||||
|
||||
# Domain name of the server
|
||||
# Domain name of the server. This is required.
|
||||
HTTP_DOMAIN=domain.com
|
||||
|
||||
# Root of the HTTP server. Defaults to "/"
|
||||
# If you host other things on your domain, you may want to update this to be "/bans" or something.
|
||||
#HTTP_ROOT=/
|
||||
|
||||
# Static files handler. Defaults to "local"
|
||||
# Valid values are:
|
||||
# * local
|
||||
# * remote
|
||||
# Locally handled static files use the STATIC_LOCAL_PATH config value.
|
||||
# IN GENERAL, the "local" configuration should not be used in a production environment.
|
||||
#STATIC_HANDLER=local
|
||||
|
||||
# The local path to serve static files out of. Defaults to "static"
|
||||
# This is only used when STATIC_HANDLER is set to "local".
|
||||
#STATIC_LOCAL_PATH=static
|
||||
|
||||
# Whether to follow symlinks in the local static file handler. Defaults to "true"
|
||||
# This is only used when STATIC_HANDLER is set to "local".
|
||||
# Must be one of:
|
||||
# * 1, true, yes
|
||||
# * 0, false, no
|
||||
#STATIC_LOCAL_FOLLOW_SYMLINKS=true
|
||||
|
||||
# This is the URL to map static files to. Defaults to /static
|
||||
# This *WILL NOT* prepend the HTTP_ROOT path.
|
||||
#STATIC_ROOT=/static
|
||||
|
||||
Reference in New Issue
Block a user