embeddable writing updates https://sillywordz.kissing.computer/
Find a file
2025-11-26 09:38:00 +00:00
.idea add storage and model 2021-11-22 09:05:57 +01:00
assets ok 2025-11-22 00:44:49 -05:00
config formatting 2022-02-12 16:14:46 +01:00
model fndf 2025-11-19 22:21:08 -05:00
storage fixed deleting and editing also all status show up on homepage now 2025-11-26 04:32:58 -05:00
vpub formatting 2022-02-12 16:14:46 +01:00
web fixed deleting and editing also all status show up on homepage now 2025-11-26 04:32:58 -05:00
.env.example updates 2025-05-15 17:08:32 -04:00
.gitignore ok 2025-11-22 00:44:49 -05:00
docker-compose.yml ok 2025-11-22 00:44:49 -05:00
Dockerfile ok 2025-11-22 00:44:49 -05:00
generate.go Add web package 2021-11-22 10:06:23 +01:00
go.mod Adding TOS 2021-12-24 12:27:11 +01:00
go.sum Adding TOS 2021-12-24 12:27:11 +01:00
LICENSE Add license 2021-12-04 16:24:02 +01:00
main.go ok 2025-11-22 00:44:49 -05:00
Makefile Add endpoint to get status as json 2021-11-24 07:30:19 +01:00
README.md Update README.md 2025-11-26 09:38:00 +00:00

this is a fork of status.cafe that is for embeddable writing updates. dockerization credit to melo, girlonthemoon.xyz, who wrote the below documentatipn:

this is just a clone of ~m15o/status that adds a dockerfile and compose file for containerized deployment.

customization and administration

the following environment variables in .env.example configure administration and customization of the site. please copy the example file to .env for it to work with the compose file.

  • DATABASE_URL - the value for this will fill in with variables that configure postgres in the same file, which you should change for security.
  • ASSETS_DIR - the value provided should not be changed unless you wish to move the assets folder in the source code. on the host, the asset directory can contain style2.css, which is mounted over the style.css file in the container via the compose file, to allow for customization of the site's styling.
  • MANUAL_REGISTRATION - by default this is disabled, which means all users are automatically approved upon registration and are able to post. after registering a user you will use as admin, i recommend setting this to 0 to enable manual approval of users via the /admin page.

in web/handler/admin_show.go, you must edit all instances of m15o to reflect your admin account's username, or else you will not be able to access the admin page and approve/deny users.