docker/bluesky-pds.md

@@ -4,12 +4,11 @@ draft: false
 date: 2025-01-18
 ---
 
-|               |                                                                                                          |
+|              |                                                                                                          |
-| ------------- | -------------------------------------------------------------------------------------------------------- |
+| ------------ | -------------------------------------------------------------------------------------------------------- |
-| image         | [quartz-docker image](https://code.modernleft.org/gravityfargo/-/packages/container/bluesky-pds/latest)  |
+| image        | [quartz-docker image](https://code.modernleft.org/gravityfargo/-/packages/container/bluesky-pds/latest)  |
-| base project  | [GitHub - bluesky-social/pds](https://github.com/bluesky-social/pds)                                     |
+| base project | [GitHub - bluesky-social/pds](https://github.com/bluesky-social/pds)                                     |
-| image source  | [Forgejo - gravityfargo/bluesky-pds-docker](https://code.modernleft.org/gravityfargo/bluesky-pds-docker) |
+| image source | [Forgejo - gravityfargo/bluesky-pds-docker](https://code.modernleft.org/gravityfargo/bluesky-pds-docker) |
-| Issue Tracker | [GitHub - gravityfargo/bluesky-pds-docker](https://github.com/gravityfargo/bluesky-pds-docker)           |
 
 ```bash
 docker pull code.modernleft.org/gravityfargo/bluesky-pds:latest
@@ -36,7 +35,7 @@ I haven't verified these are the minimum requirements, but they are what I found
 sudo pacman -S jq
 ```
 
-#### Debian/Ubuntu
+#### Debian/Ubunutu
 
 ```bash
 sudo apt install make xxd
@@ -44,8 +43,7 @@ sudo apt install make xxd
 
 ### Setup
 
-Generate secrets and add them to `.env` file.
+Generate secrets and add them to `.env` file. See [example.env](example.env) as an example.
-See [example.env](https://code.modernleft.org/gravityfargo/bluesky-pds-docker/src/branch/main/example.env) as an example.
 
 ```bash
 # Generate secret environment variables
@@ -58,38 +56,17 @@ echo PDS_PLC_ROTATION_KEY_K256_PRIVATE_KEY_HEX: $(openssl ecparam --name secp256
 
 ### Docker Compose Setup
 
-Full list of additional Environment Variables provided by bluesky upstream can be found in the
+Full list of additional Environment Variables provided by bluesky upstream can be found in the [packages/pds/src/config/env.ts](https://github.com/bluesky-social/atproto/blob/main/packages/pds/src/config/env.ts)
-[packages/pds/src/config/env.ts](https://github.com/bluesky-social/atproto/blob/main/packages/pds/src/config/env.ts)
 
-By default, the image uses 1000:1000 as the UID:GID for the user. This can be changed by setting the `PUID` and `PGID` environment variables.
+By default, the image uses 1000:1000 as the UID:GID for the user. This can be changed by setting the `PUID` and `PGID` environment variables. The compose element `hostname` must be the same value as `PDS_HOSTNAME`.
-The compose element `hostname` must be the same value as `PDS_HOSTNAME`.
 
 ![[traefik]]
 ![[standalone]]
 
-### Running Commands
-
-Nothing has changed in this department, other than not needing `sudo`. The commands are the same as the upstream project. Such as
-
-- [Creating an account using pdsadmin](https://github.com/bluesky-social/pds?tab=readme-ov-file#creating-an-account-using-pdsadmin)
-- [Creating an account using an invite code](https://github.com/bluesky-social/pds?tab=readme-ov-file#creating-an-account-using-an-invite-code)
-
-```bash
-docker exec -it bluesky-pds bash
-pdsadmin account create
-pdsadmin create-invite-code
-```
-
-> [!danger] Update Warning
-> Do not under any circumstances update the image using `pdsadmin update`. I have not tested this, and it may break the image. Submit an
-> [issue to my repository](https://github.com/gravityfargo/bluesky-pds-docker) requesting an update,
-> and I will update this image and pin the pds to the new version.
-
 ### Cloudflare DNS
-
 After various testing, I have figured out two things.
-
 1. In order for email verification to work, you cannot have the DNS Proxy enabled or `AAAA` records active.
 2. After you have verified emails, and do not intend to use the email feature, you can re-enable the DNS Proxy and `AAAA` records.
 
+
 ![[bluesky-pds-cloudflare.png]]