"production", "branch": "main", "root": "/absolute/path/to/code/root", } Everything else is integrated automatically, you will now collect both server and client side errors. Migrating Weblate to another edit the port mapping in the docker-compose.override.yml file to change it. 3. Start Weblate containers: docker-compose up Enjoy your Weblate deployment, it’s accessible on port 80 of the weblate container Weblate container. Changed in version 3.7.1-6: In July 2019 (starting with the 3.7.1-6 tag), the containers are not running as a root user. This has changed the exposed port from 80 to 8080. See also Invoking

"production", "branch": "main", "root": "/absolute/path/to/code/root", } Everything else is integrated automatically, you will now collect both server and client side errors. Migrating Weblate to another edit the port mapping in the docker-compose.override.yml file to change it. 3. Start Weblate containers: docker-compose up Enjoy your Weblate deployment, it’s accessible on port 80 of the weblate container Weblate container. Changed in version 3.7.1-6: In July 2019 (starting with the 3.7.1-6 tag), the containers are not running as a root user. This has changed the exposed port from 80 to 8080. See also Invoking

"production", "branch": "main", "root": "/absolute/path/to/code/root", } Everything else is integrated automatically, you will now collect both server and client side errors. Migrating Weblate to another edit the port mapping in the docker-compose.override.yml file to change it. 3. Start Weblate containers: docker-compose up Enjoy your Weblate deployment, it’s accessible on port 80 of the weblate container Weblate container. Changed in version 3.7.1-6: In July 2019 (starting with the 3.7.1-6 tag), the containers are not running as a root user. This has changed the exposed port from 80 to 8080. See also Invoking

"production", "branch": "main", "root": "/absolute/path/to/code/root", } Everything else is integrated automatically, you will now collect both server and client side errors. Migrating Weblate to another edit the port mapping in the docker-compose.override.yml file to change it. 3. Start Weblate containers: docker-compose up Enjoy your Weblate deployment, it’s accessible on port 80 of the weblate container Weblate container. Changed in version 3.7.1-6: In July 2019 (starting with the 3.7.1-6 tag), the containers are not running as a root user. This has changed the exposed port from 80 to 8080. See also Invoking

"production", "branch": "main", "root": "/absolute/path/to/code/root", } Everything else is integrated automatically, you will now collect both server and client side errors. Migrating Weblate to another edit the port mapping in the docker-compose.override.yml file to change it. 3. Start Weblate containers: docker-compose up Enjoy your Weblate deployment, it’s accessible on port 80 of the weblate container Weblate container. Changed in version 3.7.1-6: In July 2019 (starting with the 3.7.1-6 tag), the containers are not running as a root user. This has changed the exposed port from 80 to 8080. See also Invoking

"production", "branch": "main", "root": "/absolute/path/to/code/root", } Everything else is integrated automatically, you will now collect both server and client side errors. Migrating Weblate to another edit the port mapping in the docker-compose.override.yml file to change it. 3. Start Weblate containers: docker-compose up Enjoy your Weblate deployment, it’s accessible on port 80 of the weblate container Weblate container. Changed in version 3.7.1-6: In July 2019 (starting with the 3.7.1-6 tag), the containers are not running as a root user. This has changed the exposed port from 80 to 8080. See also Invoking

"production", "branch": "main", "root": "/absolute/path/to/code/root", } Everything else is integrated automatically, you will now collect both server and client side errors. Migrating Weblate to another edit the port mapping in the docker-compose.override.yml file to change it. 3. Start Weblate containers: docker-compose up Enjoy your Weblate deployment, it’s accessible on port 80 of the weblate container Weblate container. Changed in version 3.7.1-6: In July 2019 (starting with the 3.7.1-6 tag), the containers are not running as a root user. This has changed the exposed port from 80 to 8080. See also Invoking

"production", "branch": "main", "root": "/absolute/path/to/code/root", } Everything else is integrated automatically, you will now collect both server and client side errors. Migrating Weblate to another edit the port mapping in the docker-compose.override.yml file to change it. 3. Start Weblate containers: docker-compose up Enjoy your Weblate deployment, it’s accessible on port 80 of the weblate container Weblate container. Changed in version 3.7.1-6: In July 2019 (starting with the 3.7.1-6 tag), the containers are not running as a root user. This has changed the exposed port from 80 to 8080. See also Invoking

"production", "branch": "main", "root": "/absolute/path/to/code/root", } Everything else is integrated automatically, you will now collect both server and client side errors. Migrating Weblate to another edit the port mapping in the docker-compose.override.yml file to change it. 3. Start Weblate containers: docker-compose up Enjoy your Weblate deployment, it’s accessible on port 80 of the weblate container Weblate container. Changed in version 3.7.1-6: In July 2019 (starting with the 3.7.1-6 tag), the containers are not running as a root user. This has changed the exposed port from 80 to 8080. See also Invoking

"production", "branch": "main", "root": "/absolute/path/to/code/root", } Everything else is integrated automatically, you will now collect both server and client side errors. Migrating Weblate to another edit the port mapping in the docker-compose.override.yml file to change it. 3. Start Weblate containers: docker-compose up Enjoy your Weblate deployment, it’s accessible on port 80 of the weblate container Weblate container. Changed in version 3.7.1-6: In July 2019 (starting with the 3.7.1-6 tag), the containers are not running as a root user. This has changed the exposed port from 80 to 8080. See also Invoking