kutt/docker-compose.yml

services:
  server:
    build:
      context: .
    volumes:
       - db_data_sqlite:/var/lib/kutt
       - custom:/kutt/custom
    environment:
      DB_FILENAME: "/var/lib/kutt/data.sqlite"
    ports:
      - 3000:3000
volumes:
  db_data_sqlite:
  custom:
Add docker-compose file and improve dockerfile 2019-06-22 15:43:49 +04:30			`services:`
update and add docker files for v3 2025-01-08 09:47:03 +03:30			`server:`
			`build:`
			`context: .`
feat: sanitize docker-compose (#360) * Sanitize docker-compose - remove the container names since this is not mandatory and the feature is not used. - remove the network since all containers can communicate with each other when using docker-compose. - add persistence to the databases to avoid the loss of data. * Add .env file for docker This is a copy of the `.example.env`-file with some settings changed to work with the docker-compose file 2020-07-28 17:01:53 +02:00			`volumes:`
update and add docker files for v3 2025-01-08 09:47:03 +03:30			`- db_data_sqlite:/var/lib/kutt`
change docker work directory back to kutt for backward compatibility 2025-01-16 11:16:23 +03:30			`- custom:/kutt/custom`
Add docker-compose file and improve dockerfile 2019-06-22 15:43:49 +04:30			`environment:`
update and add docker files for v3 2025-01-08 09:47:03 +03:30			`DB_FILENAME: "/var/lib/kutt/data.sqlite"`
			`ports:`
			`- 3000:3000`
feat: sanitize docker-compose (#360) * Sanitize docker-compose - remove the container names since this is not mandatory and the feature is not used. - remove the network since all containers can communicate with each other when using docker-compose. - add persistence to the databases to avoid the loss of data. * Add .env file for docker This is a copy of the `.example.env`-file with some settings changed to work with the docker-compose file 2020-07-28 17:01:53 +02:00			`volumes:`
add custom folder volume to docker compositions 2025-01-15 11:49:30 +03:30			`db_data_sqlite:`
			`custom:`