gravityfargo/bluesky-pds-docker
1
0
Fork 0
Code Issues 1 Pull requests Packages 1 Activity
A self contained Bluesky PDS
11 commits 2 branches 0 tags 145 KiB
Dockerfile 54.9%
Shell 26.8%
Makefile 18.3%
Find a file
Nathan Price 5a250e442b
init
2024-12-03 17:47:58 -05:00
.dockerignore init 2024-12-03 17:47:58 -05:00
.gitignore bump 2024-12-02 20:43:33 -05:00
docker-compose.yaml hardcoded hostname, changed volume bind 2024-12-02 20:42:39 -05:00
Dockerfile added labels 2024-12-02 20:42:16 -05:00
entrypoint.sh init 2024-12-01 19:15:39 -05:00
LICENSE add license 2024-12-02 20:35:09 -05:00
Makefile using more variables 2024-12-02 20:42:57 -05:00
README.md bump 2024-12-02 20:44:33 -05:00

README.md

bluesky-pds-docker

It is required to set the hostname of the container to your FQDN or use host networking on a server whose hostname is the FQDN.

Deployment

git clone https://forgejo.gravityfargo.dev/gravityfargo/bluesky-pds-docker.git && cd bluesky-pds-docker

make create-config
make generate-secrets
# edit the config/pds.env file to set the FQDN

docker pull forgejo.gravityfargo.dev/gravityfargo/bluesky-pds:0.4.74
docker-compose up -d

Example Docker Compose

services:
  bluesky-pds:
    container_name: bluesky-pds
    hostname: sheltersky.social
    image: bluesky-pds:0.4.74
    ports:
      - 3000:3000
    volumes:
      - ./config:/pds

Contributing

  • Fork and clone the repository
  • make build to build the image

It's my preference not to host any code on GitHub, but I've enabled signing in with Github because most people already have that, and I don't want the hassle of a new login to prevent contributors. You cannot create new repositories on this Forgejo instance, but forking is allowed. The upstream PDS repository is on Github.