pds dash for shimaenaga.veryroundbird.house (based off of pds.witchcraft.systems)
veryroundbird.house
1# carly's shimaenaga pds version
2
3uhhh the differences here are
4
5* I wrote my own theme CSS. it's one-column and makes the account cards smaller (just avatars)
6* Reorganized CSS
7* Modified markup a bit to use the HTML popover API to show user info cards instead of just linking to the account
8* Added some stuff in the backend code to also pull the user's description and banner to make the account cards fancier
9* Changed font to Recursive Variable (waffling on changing this to space mono though and maybe using recursive just for the profile cards)
10* Replaced favicon
11* Ported in guestbook functionality from another PDS frontpage (see new config options)
12* Secret unique easter egg :)
13* Wrote deploy pipeline for tangled.sh (WORK IN PROGRESS help try #5 - changing ssh perms?)
14
15you can see it running at [my pds!](https://shimaenaga.veryroundbird.house)
16
17# original readme below this line
18
19a frontend dashboard with stats for your ATProto PDS.
20
21## setup
22
23### prerequisites
24
25- [deno](https://deno.com/manual/getting_started/installation)
26
27### installing
28
29clone the repo, copy `config.ts.example` to `config.ts` and edit it to your liking.
30
31then, install dependencies using deno:
32
33```sh
34deno install
35```
36
37### development server
38
39local develompent server with hot reloading:
40
41```sh
42deno task dev
43```
44
45### building
46
47to build the optimized bundle run:
48
49```sh
50deno task build
51```
52
53the output will be in the `dist/` directory.
54
55## deploying
56
57we use our own CI/CD workflow at [`.forgejo/workflows/deploy.yaml`](.forgejo/workflows/deploy.yaml), but it boils down to building the project bundle and deploying it to a web server. it'll probably make more sense to host it on the same domain as your PDS, but it doesn't affect anything if you host it somewhere else.
58
59## configuring
60
61[`config.ts`](config.ts) is the main configuration file, you can find more information in the file itself.
62
63## theming
64
65themes are located in the `themes/` directory, you can create your own theme by copying one of the existing themes and modifying it to your liking.
66
67currently, the name of the theme is determined by the directory name, and the theme itself is defined in `theme.css` inside that directory.
68
69you can switch themes by changing the `theme` property in `config.ts`.
70
71the favicon is located at [`public/favicon.ico`](public/favicon.ico)
72
73## license
74
75MIT