···11# pds-dash
2233-A fork of [pds-dash](https://git.witchcraft.systems/scientific-witchery/pds-dash) for [selfhosted.social](https://selfhosted.social). The top part of the readme is about this fork.
44-See after [Original Readme](#original-readme) to see the original readme for setup
33+A fork of
44+[pds-dash](https://git.witchcraft.systems/scientific-witchery/pds-dash) for
55+[selfhosted.social](https://selfhosted.social). The top part of the readme is
66+about this fork. See after [Original Readme](#original-readme) to see the
77+original readme for setup
5869This fork is much the same but a few differences:
1010+711- [New theme](/themes/dark/theme.css)
88-- Uses the CDN for loading images and videos instead of `com.atproto.sync.getBlob`
99-- Caches a couple of things like did -> handle and PDS user profile lexicon inside localstorage. Not the best, but was simpler and has a expire on get.
1212+- Uses the CDN for loading images and videos instead of
1313+ `com.atproto.sync.getBlob`
1414+- Caches a couple of things like did -> handle and PDS user profile lexicon
1515+ inside localstorage. Not the best, but was simpler and has a expire on get.
1016- The text "Home to x accounts" only shows active accounts.
1117- I did add a sponsor button for my GitHub.
12181313-An example of a caddy file you can use
1919+An example of a caddy file you can use
2020+1421```caddyfile
1522 # Should be all the endpoints a PDS calls
1623 @pds {
···3138 try_files {path} /index.html
3239 file_server
3340 }
3434-3541```
3636-37423843# Original Readme
3944···47524853### installing
49545050-clone the repo, copy `config.ts.example` to `config.ts` and edit it to your liking.
5555+clone the repo, copy `config.ts.example` to `config.ts` and edit it to your
5656+liking.
51575258then, install dependencies using deno:
5359···75817682## deploying
77837878-we 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.
8484+we use our own CI/CD workflow at
8585+[`.forgejo/workflows/deploy.yaml`](.forgejo/workflows/deploy.yaml), but it boils
8686+down to building the project bundle and deploying it to a web server. it'll
8787+probably make more sense to host it on the same domain as your PDS, but it
8888+doesn't affect anything if you host it somewhere else.
79898090## configuring
81918282-[`config.ts`](config.ts) is the main configuration file, you can find more information in the file itself.
9292+[`config.ts`](config.ts) is the main configuration file, you can find more
9393+information in the file itself.
83948495## theming
85968686-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.
9797+themes are located in the `themes/` directory, you can create your own theme by
9898+copying one of the existing themes and modifying it to your liking.
87998888-currently, the name of the theme is determined by the directory name, and the theme itself is defined in `theme.css` inside that directory.
100100+currently, the name of the theme is determined by the directory name, and the
101101+theme itself is defined in `theme.css` inside that directory.
8910290103you can switch themes by changing the `theme` property in `config.ts`.
91104