The feature is actually already done on my side(so I can just add in new post scheduling jobs). I’m just letting it do a test run on dev to see if there’s anything messed up with the cron scheduling and db table locking.
you’re accessing the lemmy db directly instead of using the lemmy api? (or on second reading, perhaps your code uses its own separate db to keep track of things?)
The feature is actually already done on my side(so I can just add in new post scheduling jobs). I’m just letting it do a test run on dev to see if there’s anything messed up with the cron scheduling and db table locking.
you’re accessing the lemmy db directly instead of using the lemmy api? (or on second reading, perhaps your code uses its own separate db to keep track of things?)
I’m using the api, but I’m also using a database schema to store data that is specifically used by the bot.