This action will delete this post on this instance and on all federated instances, and it cannot be undone. Are you certain you want to delete this post?
This action will block this actor and hide all of their past and future posts. Are you certain you want to block this actor?
This action will block this object. Are you certain you want to block this object?
Are you sure you want to delete the OAuth client [Client Name]? This action cannot be undone and will revoke all access tokens for this client.
Are you sure you want to revoke the OAuth token [Token ID]? This action cannot be undone and will immediately revoke access for this token.
Epiktistes is my home in the Fediverse. It is an instance of Ktistec, a single-user ActivityPub server like Mastodon, but with fewer users and fewer commits. Here's my introduction (last updated early-2025).
I wrote a series of posts about optimizing the performance of the Ktistec server, its build time, and its executable size: part 1, part 2, part 3, part 4, and part 5.
Some things I regularly write about, organized by hashtag:
I also wrote some #pointfreeverse.
new artwork next to the elevator outside the office #mulberryst #nyc
woop! upstream already had the change to `package.json`.
@broken@mastodon.social no problem... the chain of steps starts with "In `package.json`...". I guess I could have numbered them, too. :-/
@Gargron@mastodon.social your current Docker solution is actually pretty nice. I ended up on Heroku because I already had a dozen projects on there. now I have an even thirteen...
@Gargron@mastodon.social I'm definitely interested. I'll wrap these up in a PR and start a discussion.
@broken@mastodon.social I posted several follow-up messages with more detail (unfortunately, I didn't use the reply to chain them).
@Gargron@mastodon.social uhhh, right :-( need an edit button...
Configure SMTP or users won't be able to activate new accounts. Definitely configure S3 for file storage, or your uploads (uploaded to `tmp`) will disappear every time the Heroku dyno restarts!
Finish by configuring the Heroku environment (using `.env.production.sample` as a guide). Definitely configure `LOCAL_DOMAIN` and `LOCAL_HTTPS` correctly. (I didn't do this immediately and as a consequence the first handful of people I followed saw me as a user on an instance running on `localhost`.) For `PAPERCLIP_SECRET` and `SECRET_KEY_BASE` I ran `rake secret` in another Rails project to generate the secret keys.
Fix Paperclip by changing `s3_permissions` from "public" to "public-read" in `config/initializers/paperclip.rb`. I'm pretty sure this is a bug. I need to investigate a bit more and then submit a PR.