RadDevon

@RadDevon@lemmy.zip

• ⁨Comment⁩ on ⁨Help needed with selfhosting Obsidian/FOSS way to publish obsidian?⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  Seconding Quartz, but I also wanted to share how I self-host all the services required. I self-host Forgejo and use obsidian-git to make it easier to push my vault changes to my self-hosted repo. The repo has a workflow that runs the Quartz build on any new commit, building to a location my web server points to.

  It works pretty well. About 2 minutes after a change is pushed, the build with those changes is done and being served.

• ⁨Comment⁩ on ⁨Portabase v1.7.1 - Open source database backup/restore tool⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  Thanks for the clarification. By “persist across restarts,” I’m referring to the fact that if I just install the agent in my container, it won’t persist if I restart the container, unless I install it on a volume which seems clunky. Running the agent alongside in a separate container with network access is the solution I was looking for.

  On the Redis and Valkey restores, that makes sense. Disaster recovery is my use case anyway. Do you document the manual restore process for those? I didn’t notice it in a brief review of the docs, but I may have overlooked it.

• ⁨Comment⁩ on ⁨Portabase v1.7.1 - Open source database backup/restore tool⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  This looks exciting! A couple of questions:

  1. How would I deploy an agent into an existing docker container in a way that makes it persist across restarts? Most of my databases are running in containers.
  2. Regarding redis and valkey: what good does backup do without restore? Not trying to denigrate; I just really want to understand how that is useful.

  Thanks for building this!