Bind to ‘localhost’ instead of ‘0.0.0.0’ by default
This is a small safety precaution to make sure the out of the box configuration is not world routeable. Bringing this up on a public interface with a connected database could be a security concern. Any sysadmin worth their salt is going to test offline or by binding to localhost only first anyway, but this gets them started on the right foot and makes sure people don't make mistakes. Also with the high likelihood that a proxy is going to be used for HTTPS termination anyway, the decision to move to a public IP should be more deliberate.
This commit is contained in:
parent
6c40e05d2d
commit
26a023813e
1 changed files with 1 additions and 1 deletions
|
@ -1,6 +1,6 @@
|
|||
[app]
|
||||
# Interface and port where the app will run its webserver.
|
||||
address = "0.0.0.0:9000"
|
||||
address = "localhost:9000"
|
||||
|
||||
# BasicAuth authentication for the admin dashboard. This will eventually
|
||||
# be replaced with a better multi-user, role-based authentication system.
|
||||
|
|
Loading…
Reference in a new issue