veryroundbird.house / pds-dash
pds dash for shimaenaga.veryroundbird.house (based off of pds.witchcraft.systems)
fork atom
CSS 30.3%
Svelte 24.4%
TypeScript 16.0%
HTML 0.4%
JavaScript 0.3%
Other 28.6%
55 1 0

Clone this repository

https://tangled.org/veryroundbird.house/pds-dash
git@nest.veryroundbird.house:veryroundbird.house/pds-dash

For self-hosted knots, clone URLs may differ based on your setup.

Download tar.gz
README.md

carly's shimaenaga pds version#

uhhh the differences here are

  • I wrote my own theme CSS. it's one-column and makes the account cards smaller (just avatars)
  • Reorganized CSS
  • Modified markup a bit to use the HTML popover API to show user info cards instead of just linking to the account
  • Added some stuff in the backend code to also pull the user's description and banner to make the account cards fancier
  • Changed font to Recursive Variable (waffling on changing this to space mono though and maybe using recursive just for the profile cards)
  • Replaced favicon
  • Ported in guestbook functionality from another PDS frontpage (see new config options)
  • Secret unique easter egg :)
  • Wrote deploy pipeline for tangled.sh (WORK IN PROGRESS help try #5 - changing ssh perms?)

you can see it running at my pds!

original readme below this line#

a frontend dashboard with stats for your ATProto PDS.

setup#

prerequisites#

installing#

clone the repo, copy config.ts.example to config.ts and edit it to your liking.

then, install dependencies using deno:

deno install

development server#

local develompent server with hot reloading:

deno task dev

building#

to build the optimized bundle run:

deno task build

the output will be in the dist/ directory.

deploying#

we use our own CI/CD workflow at .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.

configuring#

config.ts is the main configuration file, you can find more information in the file itself.

theming#

themes 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.

currently, the name of the theme is determined by the directory name, and the theme itself is defined in theme.css inside that directory.

you can switch themes by changing the theme property in config.ts.

the favicon is located at public/favicon.ico

license#

MIT