archive/bramw_baserow
1
0
Fork 0
mirror of https://gitlab.com/bramw/baserow.git synced 2025-04-17 18:32:35 +00:00
Code Issues Projects Releases Wiki Activity

Allow 127.0.0.1 to make self hosting easier + add an env...

Browse source
This commit is contained in:
Nigel Gott 2022-05-06 15:55:50 +00:00
parent e720b00c86
commit 0a37fc640c
5 changed files with 9 additions and 2 deletions
backend/src/baserow/config/settings
base.py
changelog.md
deploy/all-in-one/supervisor
default_baserow_env.sh
docker-compose.yml
docs/installation
configuration.md

3
backend/src/baserow/config/settings/base.py
View file

@ -17,7 +17,8 @@ if "SECRET_KEY" in os.environ:
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = os.getenv("BASEROW_BACKEND_DEBUG", "off") == "on"
ALLOWED_HOSTS = ["localhost"]
ALLOWED_HOSTS = ["localhost", "127.0.0.1"]
ALLOWED_HOSTS += os.getenv("BASEROW_EXTRA_ALLOWED_HOSTS", "").split(",")
INSTALLED_APPS = [
"django.contrib.auth",

3
changelog.md
View file

@ -54,6 +54,9 @@
* **Premium** Added row coloring.
* Fixed row coloring bug when the table doesn't have any single select field.
* Dropdown can now be focused with tab key
* Added 0.0.0.0 and 127.0.0.1 as ALLOWED_HOSTS for connecting to the Baserow backend
* Added a new BASEROW_EXTRA_ALLOWED_HOSTS optional comma separated environment variable
for configuring ALLOWED_HOSTS.
## Released (2022-03-03 1.9.1)

3
deploy/all-in-one/supervisor/default_baserow_env.sh
View file

@ -38,8 +38,9 @@ export BASEROW_CADDY_GLOBAL_CONF="${BASEROW_CADDY_GLOBAL_CONF:-}"
export PRIVATE_BACKEND_URL='http://localhost:8000'
export PRIVATE_WEB_FRONTEND_URL='http://localhost:3000'
export BASEROW_BACKEND_BACKEND_PORT=127.0.0.1
export BASEROW_BACKEND_BIND_ADDRESS=127.0.0.1
export BASEROW_WEBFRONTEND_BIND_ADDRESS=127.0.0.1
export BASEROW_EXTRA_ALLOWED_HOSTS="${BASEROW_EXTRA_ALLOWED_HOSTS:-}"
export DJANGO_SETTINGS_MODULE=${DJANGO_SETTINGS_MODULE:-'baserow.config.settings.base'}
export SYNC_TEMPLATES_ON_STARTUP=${SYNC_TEMPLATES_ON_STARTUP:-true}

1
docker-compose.yml
View file

@ -154,6 +154,7 @@ x-common-backend-variables: &common-backend-variables
FROM_EMAIL:
DISABLE_ANONYMOUS_PUBLIC_VIEW_WS_CONNECTIONS:
MEDIA_URL:
BASEROW_EXTRA_ALLOWED_HOSTS:
services:
# A caddy reverse proxy sitting in-front of all the services.

1
docs/installation/configuration.md
View file

@ -27,6 +27,7 @@ The installation methods referred to in the variable descriptions are:
| PUBLIC\_BACKEND\_URL | Please use BASEROW\_PUBLIC\_URL unless you are using the standalone baserow/backend or baserow/web-frontend images. The publicly accessible URL of the backend. Should include the port if non-standard. Ensure BASEROW\_PUBLIC\_URL is set to an empty value to use this variable in the compose setup. | $BASEROW\_PUBLIC\_URL, http://localhost:8000/ in the standalone images. |
| PUBLIC\_WEB\_FRONTEND\_URL | Please use BASEROW\_PUBLIC\_URL unless you are using the standalone baserow/backend or baserow/web-frontend images. The publicly accessible URL of the web-frontend. Should include the port if non-standard. Ensure BASEROW\_PUBLIC\_URL is set to an empty value to use this variable in the compose setup. | $BASEROW\_PUBLIC\_URL, http://localhost:3000/ in the standalone images. |
| WEB\_FRONTEND\_PORT | The HTTP port that is being used to access Baserow using. Only used by the docker-compose files. | Only used by the docker-compose.yml files, defaults to 80 but prior to 1.9 defaulted to 3000. |
| BASEROW\_EXTRA\_ALLOWED\_HOSTS | An optional comma separated list of hostnames which will be added to the Baserow's Django backend [ALLOWED_HOSTS](https://docs.djangoproject.com/en/4.0/ref/settings/#allowed-hosts) setting. In most situations you will not need to set this as the hostnames from BASEROW\_PUBLIC\_URL or PUBLIC\_BACKEND\_URL will be added to the ALLOWED_HOSTS automatically. This is only needed if you need to allow additional different hosts to be able to access your Baserow. | |
| PRIVATE\_BACKEND\_URL | **Only change this with standalone images.** This is the URL used when the web-frontend server directly queries the backend itself when doing server side rendering. As such not only the browser, but also<br>the web-frontend server should be able to make HTTP requests to the backend. The web-frontend nuxt server might not have access to the \`PUBLIC\_BACKEND\_URL\` or there could be a more direct route, (e.g. from container to container instead of via the internet). For example if the web-frontend and backend were containers on the same docker network this could be set to http://backend:8000. | |
| BASEROW\_CADDY\_GLOBAL\_CONF | **Not supported by standalone images.** Will be substituted into the Caddyfiles global config section. Set to “debug” to enable Caddies debug logging. | |
| BASEROW\_CADDY\_EXTRA\_CONF | **Not supported by standalone images.** Will be substituted into the end of the Caddyfiles server block | |