Further, we provide tips for running The Things Stack in production. Settings in docker-compose.yml and ttn-lw-stack-docker.yml files are explained in detail in Understanding Docker Configuration and Understanding The Things Stack Configuration sections.
#Docker ip configuration update
Be sure to update ttn-lw-stack-docker.yml with your server address, generate keys in okie and set -secret.įor an extended explanation of the configuration settings, keep reading. These example configuration files contain all of the configuration settings you need to run The Things Stack for development. This guide assumes the following directory hierarchy:ĭownload the example docker-compose.yml for The Things Stack Enterprise here.ĭownload the example ttn-lw-stack-docker.yml for The Things Stack Enterprise here.ĭownload the example docker-compose.yml for The Things Stack Open Source here.ĭownload the example ttn-lw-stack-docker.yml for The Things Stack Open Source here. See the Configuration Reference for more information about the configuration options. All configuration options have a corresponding environment variable and command-line flag. The configuration options in ttn-lw-stack-docker can also be specified using command-line flags or environment variables. When The Things Stack starts, it searches through ttn-lw-stack-docker.yml for component server addresses, a TLS certificate source, client authentication credentials, and other configuration parameters. Ttn-lw-stack-docker.yml contains the configuration specific to The Things Stack deployment and is used to configure The Things Stack. docker-compose.ymlĭocker-compose.yml defines the Docker services of The Things Stack and its dependencies, and is used to configure Docker. 3.The Things Stack requires two configuration files when installing with Docker: docker-compose.yml and ttn-lw-stack-docker.yml.Įxample files for Enterprise and Open source are provided below. For each service, the stack file also describes service specific configuration that must be present before the application boots.
#Docker ip configuration software
What's happening here? The stack file describes three services called web - the Wireguardian Access Server container image, db - a Postgres database, and traefik - a software defined network router.
#Docker ip configuration password
In this case, the database password and secret key base will be automatically generated. Note: The docker-compose.yml file can be also be automatically generated with our Quickstart Scripts. should be the IT administrator email address that you wish to associate with the Let's Encrypt SSL certificate for the. should specify the full-qualified hostname of your deployment, e.g.,. should be a 32-length random alpha-numeric string, and specifies the secret key used to encrypt session storage, authentication cookies, and XSRF protection tokens for the administrator and user web-portals. Please replace the placeholders, ,, and in the above file with values that are appropriate for your deployment. letsencrypt:/letsencrypt labels : # Redirect all HTTP to HTTPS permanently - _le=HostRegexp(``) - _catchall.entrypoints=web - _catchall.middlewares=https_redirect - _=https - _=true volumes : database : networks : wg_internal : external : false wireguardian_wg_ingress : external : true conf:/app/config/wireguard labels : - " traefik.enable=true" - " =wg_internal" - " .=5000" - " .rule=Host(``)" - " .tls=true" - " .tls.certresolver=le" restart : always db : image : postgres:12-alpine environment : - POSTGRES_USER=postgres - POSTGRES_PASSWORD= expose : - " 5432" volumes : - " database:/var/lib/postgresql/data" networks : - wg_internal restart : always traefik : container_name : traefik image : traefik:v2.2 command : - " -api.insecure=true" - " -providers.docker=true" - " =false" - " =:80" - " .entryPoint.to=websecure" - " .entryPoint.scheme=https" - " .entrypoint.permanent=true" - " =:443" - " -certificatesResolvers.le.acme.email=" - " -certificatesresolvers.le.acme.storage=/letsencrypt/acme.json" - " -certificatesResolvers.le.acme.tlsChallenge=true" - " -certificatesResolvers.le.acme.httpChallenge=true" - " -certificatesResolvers.le.=web" restart : always ports : - 80:80 - 443:443 - 8080:8080 networks : - wg_internal - wireguardian_wg_ingress volumes : - /var/run/docker.sock:/var/run/docker.sock. Version : " 3" services : web : image : ghcr.io/kuyio/wireguardian:latest ports : - " 5000:5000" - " 51820:51820/udp" links : - db environment : PORT : 5000 DB_HOST : db DB_PORT : 5432 DB_USER : postgres DB_PASSWORD : SECRET_KEY_BASE : " " cap_add : - NET_ADMIN - SYS_MODULE sysctls : - _forward=1 - .disable_ipv6=0 networks : - wg_internal volumes :.
0 kommentar(er)
