Jill
2bfe5dc341
|
||
|---|---|---|
| src | ||
| static | ||
| .eslintignore | ||
| .eslintrc.cjs | ||
| .gitignore | ||
| .npmrc | ||
| LICENSE | ||
| README.md | ||
| flake.lock | ||
| flake.nix | ||
| jsconfig.json | ||
| package-lock.json | ||
| package.json | ||
| svelte.config.js | ||
| vite.config.js | ||
README.md
cohost-blogger
A self-hostable front-end for Cohost mimicing a CMS.
What?
CMSes are stupid to host, stupid to make and stupid to find. Why bother? We have a perfectly fine Cohost. Let's use that!
This site, pointed at a Cohost user and tag, will find every post under that tag and display it in a nice way, including the comments and proper rendering of the contents themselves.
How?
If you're on NixOS, you should be able to integrate it into your system config as a flake or just run it with nix run.
First, install the dependencies:
git clone https://git.oat.zone/oat/cohost-blogger && cd cohost-blogger
npm install
Afterwards, for development, you can run:
npm run dev
Or, for deployment:
npm run build
PORT=1234 node build
Configuration
Currently, there isn't a proper configuration system - this is not yet made to be hosted by anyone by me. You can head into src/lib/config.js for all instance-specific configuration, but this will be expanded into a proper system eventually:tm.
Attributions
- @mintexists, for help reverse-engineering the Cohost API
- Cohost's devteam - while this site does interact with Cohost, lots of the Markdown processing code is borrowed from their sourcemaps