Move to Payload CMS #3

aaron · 2026-05-11T21:07:23Z

aaron commented

2026-05-11 21:07:23 +00:00

This PR moves to payload CMS

aaron added 10 commits

2026-05-11 21:07:24 +00:00

feat: add payload 6a347c7754

feat: add payload, config and collections 71d1b5e353

chore: move to payload api 581f9e3381

chore: remove media af07e0e743

chore: move media to data dir 2adda933ad

mend

refactor: move payload-fields to src 026ce6ab0c

chore: add docker-compose cdc6312884

fix: media served via docker volume ee6f5d2d17

chore: bump to v4.0.0 b2c7db782d

chore: comment out import.ts (lazy) 533de07e22

aaron reviewed

2026-05-11 21:13:02 +00:00

docker-compose.yml

					
				@ -0,0 +5,4 @@

				    build:

				      dockerfile: ./Dockerfile

				    ports:

				      - "3010:3000"

Should move to using env vars injected into this file rather than hard-coding ports, so we can use different ports in different envs without having to commit the file back to git.

Raised issue

aaron marked this conversation as resolved

src/payload-fields.ts

					
				@ -0,0 +1,100 @@

				import { Field } from "payload";

Ideally all fields in this file should follow the optional params pattern.

Raised #5

Raised https://git.aaronjy.me/aaron/aaronjy-me/issues/5

aaron marked this conversation as resolved

src/services/content-service.ts

					
				@ -0,0 +9,4 @@

				      continue;

				    }

				    for (const tag of JSON.parse(post.tags)) {

Need to fix how tags are defined in Payload so we don't have to JSON.parse the value.

Need to fix how tags are defined in Payload so we don't have to `JSON.parse` the value.

Raised #6

Raised https://git.aaronjy.me/aaron/aaronjy-me/issues/6

aaron marked this conversation as resolved

util/import.ts

					
				@ -0,0 +1,126 @@

				// import basicPages from "./import/basic_pages_20260506-171319.json" with { type: "json" };

When running next build, this file was being built for some reason. Unsure why, though probably because tsconfig was picking it up...need to figure out a way to exclude it, and then I can uncomment the file.

When running `next build`, this file was being built for some reason. Unsure why, though probably because tsconfig was picking it up...need to figure out a way to exclude it, and then I can uncomment the file.