PocketBase as a framework, docker-compose, nginx example

[apikee]

Hope this can help someone:

Dockerfile

FROM golang:1.18 AS builder

RUN mkdir /app
ADD . /app
WORKDIR /app

RUN CGO_ENABLED=0 GOOS=linux go build -o my_app cmd/server/main.go

FROM alpine:latest AS production
COPY --from=builder /app .
CMD ["./my_app", "serve", "--http", "my_app:8090"]

docker-compose.yml (not sure if the expose is needed)

version: "3.8"

services:
  my_app:
    build: .
    container_name: my_app
    depends_on:
      - nginx
    ports:
      - "8090:8090"
    volumes:
      - my_app:/pb_data
    env_file:
      - .env.prod
    expose:
      - "8090"
    networks:
      - network

  nginx:
    image: "nginx"
    ports:
      - "80:80"
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf
    expose:
      - "80"
    networks:
      - network

volumes:
  my_app:

networks:
  network:
    driver: bridge

nginx.conf

worker_processes  1;

events {
    worker_connections  1024;
}

http {
   
  #  ...default setup

    server {
        listen 80;
        server_name my_app.com;

        location / {
            proxy_set_header Connection '';
            proxy_http_version 1.1;
            proxy_read_timeout 360s;

            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;

            proxy_pass http://my_app:8090;
        }
    }

    # ...default setup
}

[programonaut]

Hi,
thank you!

Inside the docker file you can change myapp to 0.0.0.0, so that you do not have to name you container myapp.

FROM golang:1.18 AS build-backend

RUN mkdir /app
ADD . /app
WORKDIR /app

RUN CGO_ENABLED=0 GOOS=linux go build -o <binary-name> .

FROM alpine:latest AS production
COPY --from=build-backend /app .
EXPOSE 8080
CMD ["./<binary-name>", "serve", "--http=0.0.0.0:8080"]

I also shared this and some more deployment methods in this post. Maybe it helps someone!

[woutercouvaras]

Thanks folks. Just a quick question about using docker.

I've been reading some of the discussions people have had around scaling and understand from there that PB can only scale veritcally. I'm looking into this as I try to understand deployment options, obv considering docker as one of those options.

I see from your setup that the db lives on a volume, which makes sense to use the same db as newer containers are deployed over time.

My question; how are you switching containers? From what I understand, one obviously can't use a docker swarm type of solution for rolling deployments, because of the way PB is built. Are you literally just stopping the old contianer and starting the new one? If so, what sort of lapsed time/down time are you seeing between swtiching containers?

Thanks!

[j0sh]

If so, what sort of lapsed time/down time are you seeing between swtiching containers?

For me, it is really only a couple seconds in conjunction with Docker Compose.

If zero downtime deploys are important then there are various tools for blue-green deployments around Docker / Compose, or you will need to package up Pocketbase for more sophisticated container orchestration tools like Kubernetes.