this post was submitted on 10 Aug 2023
46 points (97.9% liked)

Fediverse

17788 readers
4 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
deadsuperhero@lemmy.ml
wakest@lemmy.ml
46
App to schedule posts on Lemmy (schedule.lemmings.world)
submitted 1 year ago* (last edited 1 year ago) by rikudou@lemmings.world to c/fediverse@lemmy.ml
18 comments fedilink hide all child comments
 

I've made an app that makes it possible to schedule a post in Lemmy at an arbitrary time. It's available at https://schedule.lemmings.world and can be used by people from any instance.

Let me know what you think!

P.S. This post is made using the app!

Edit: And it's open source!

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Sal@mander.xyz 1 points 1 year ago (1 children)

I would like to make a list at some point with several community integrations and ask my instance's users whether they would like some of them installed into the instance. This application will definitely go on that list! I do need to take into consideration how many resources each of the apps consume, to make sure I don't bloat my server. But this one seems quite light. Is it?

[โ€“] rikudou@lemmings.world 4 points 1 year ago

The way I run it it's entirely serverless and costs you close to nothing.

  • the application code runs on AWS Lambda (400,000 seconds per month free, time's only counted when someone is actually making requests)
  • the static assets (CSS, JS etc.) are on S3/CloudFront (very small size, so less than $0.10)
  • event bridge scheduler is used for the scheduling (first 14,000,000 schedules per month are free)
  • sessions and "database" is in DynamoDB (you only pay for real requests, probably less than $0.10)

All in all the app can be hosted for much less than $1/month like that. If you host it in a standard docker container or something, it probably won't take much resources either, my guess would be less than 256 MB RAM (probably less than 100 MB) is needed and whatever your backend for scheduling takes (Redis would probably be the most straightforward choice).