Docker compose support

[Siumauricio]

Close #17 #73 #56

Implement docker compose deployments using Docker Compose or Docker Stack Deploy

To try out this feature you can use curl -sSL https://dokploy.com/feature.sh | sh

Compose feature

Currently we have 3 different types of deployments:

• Application
• Database
• Compose (New):
  1. Deploy via github
  2. Deploy via git
  3. Raw ( Means you paste a docker compose file and it will run )
     1. We include a random docker composition, which serves to prevent conflicts with existing services, thus saving you time by adding a prefix to each service, volume and so on.

We provide two options when creating a docker compose, the first is using docker compose, the second one is docker stack

The docker compose works in any cases, but using the docker stack deploy is for specifically use the same compose file but with less features and more focus on orchrestation (Docker Swarm)

Blog: https://vsupalov.com/difference-docker-compose-and-docker-stack/

How to test?

To test the complexity of Docker Compose, I deploy a Directus application based on the documentation. Here is the compose file: https://docs.directus.io/self-hosted/docker-guide.html#example-docker-compose

What's the difference between the link and the file below? Nothing. To make the application accessible via a domain, simply create a DNS record and add it to the labels, specifically in the Host rule.

We don't add anything to the docker compose so if you have a compose file it should work the same as in your machine.

When you deploy go to directus.dokploy.com this is in my case, make sure to update to your domain name

version: '3'
services:
  database-c42cea9b:
    image: postgis/postgis:13-master
    volumes:
      - directus-db-c42cea9b:/var/lib/postgresql/data
    environment:
      POSTGRES_USER: directus
      POSTGRES_PASSWORD: directus
      POSTGRES_DB: directus
    networks:
      - dokploy-network
  cache-c42cea9b:
    image: redis:6
    networks:
      - dokploy-network
  directus-c42cea9b:
    image: directus/directus:10.10.5
    ports:
      - '8055'
    volumes:
      - ./uploads:/directus/uploads
      - ./extensions:/directus/extensions
    depends_on:
      - cache-c42cea9b
      - database-c42cea9b
    environment:
      KEY: 255d861b-5ea1-5996-9aa3-922530ec40b1
      SECRET: 6116487b-cda1-52c2-b5b5-c8022c45e263
      DB_CLIENT: pg
      DB_HOST: database
      DB_PORT: '5432'
      DB_DATABASE: directus
      DB_USER: directus
      DB_PASSWORD: directus
      CACHE_ENABLED: 'true'
      CACHE_STORE: redis
      REDIS: redis://cache:6379
      ADMIN_EMAIL: admin@example.com
      ADMIN_PASSWORD: d1r3ctu5
    labels:
      - traefik.enable=true
      - traefik.http.routers.directus-2.rule=Host(`directus.dokploy.com`)
      - traefik.http.routers.directus-2.entrypoints=websecure
      - traefik.http.routers.directus-2.tls.certResolver=letsencrypt
      - traefik.http.services.directus-2.loadbalancer.server.port=8055
    networks:
      - dokploy-network
volumes:
  directus-db-c42cea9b: null
networks:
  dokploy-network:
    external: true

Another example deploying the official plausible repository via github

Screen.Recording.2024-05-29.at.12.44.49.AM.mp4

Pocketbase deployment in a single file

version: "3.7"
services:
  pocketbase:
    image: spectado/pocketbase:latest
    restart: unless-stopped
    ports:
      - "80"
    networks:
      - dokploy-network
    labels:
      - traefik.enable=true
      - traefik.http.routers.directus-2.rule=Host(`test2.dokploy.com`)
      - traefik.http.routers.directus-2.entrypoints=websecure
      - traefik.http.routers.directus-2.tls.certResolver=letsencrypt
      - traefik.http.services.directus-2.loadbalancer.server.port=80
    volumes:
      - /etc/dokploy/data:/pb_data
      - /etc/dokploy/public:/pb_public
      - /etc/dokploy/migrations:/pb_migrations

networks:
  dokploy-network:
    external: true

[DontFred]

Super!

[Rattlyy]

arm64 build?

[Siumauricio]

@Rattlyy Please try now, i pushed a new version including arm build