I think it's important that we make sure the Holo fork can be merged back upstream to simplify future maintenance and make things like docker configs easier. I currently have a PR open on this, so I was hoping we could reconcile our two efforts together as part of that.

I've also had AWS lambda stuff stood up for this and waiting for a couple days now. It's optimized down to ~$0.30 a month for hosting so I'm happy to take on that part of the endeavor or just transfer the virtual cloud config to you if that works better?

an AWS dashboard screenshot showing three scheduled recurring tasks for running Holo tasks

[–] virtualras@lemmy.world 4 points 1 year ago

Yeah, looks like you've put a bit more thought into the deployment that I did. I was going to run it as a scheduled task on my personal computer (I'm cheap) and was only going to move it to a cloud env if it became clear that was going to cause issues.

As for the Git repo, I took a different philosophy. Since Reddit and Lemmy are two separate entities and the dev team for the original repo showed little interest in porting it I figured I would just fork it and leave it as a new repo specific to Lemmy. I didn't want to really go through the effort of supporting both sites.

I think we can go with your setup, it solves my main concern of supporting both sites since we can both work on it. I'll PM you some of the minor things I changed to better support Lemmy. I haven't heard back from the mods since yesterday, so no threads just yet!