Update Servers/Containerization/Docker/Compose/Snipe-IT.md

This commit is contained in:
2025-04-20 23:59:35 -06:00
parent 5a3f8805db
commit 7f5851888f

View File

@ -4,7 +4,7 @@
The Snipe-IT container will attempt to launch after the MariaDB container starts, but MariaDB takes a while set itself up before it can accept connections; as a result, Snipe-IT will fail to initialize the database. Just wait about 30 seconds after deploying the stack, then restart the Snipe-IT container to initialize the database. You will know it worked if you see notes about data being `Migrated`. The Snipe-IT container will attempt to launch after the MariaDB container starts, but MariaDB takes a while set itself up before it can accept connections; as a result, Snipe-IT will fail to initialize the database. Just wait about 30 seconds after deploying the stack, then restart the Snipe-IT container to initialize the database. You will know it worked if you see notes about data being `Migrated`.
## Docker Configuration ## Docker Configuration
```jsx title="docker-compose.yml" ```yaml title="docker-compose.yml"
version: '3.7' version: '3.7'
services: services:
@ -60,7 +60,7 @@ networks:
external: true external: true
``` ```
```jsx title=".env" ```yaml title=".env"
APP_ENV=production APP_ENV=production
APP_DEBUG=false APP_DEBUG=false
APP_KEY=base64:SomethingSecure APP_KEY=base64:SomethingSecure
@ -104,7 +104,7 @@ APP_TRUSTED_PROXIES=192.168.5.29
## Traefik Reverse Proxy Configuration ## Traefik Reverse Proxy Configuration
If the container does not run on the same host as Traefik, you will need to manually add configuration to Traefik's dynamic config file, outlined below. If the container does not run on the same host as Traefik, you will need to manually add configuration to Traefik's dynamic config file, outlined below.
``` yaml ```yaml
http: http:
routers: routers:
assets: assets: