view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Do you mind expanding a bit on how you use joplin? I'm curious about the difference you found compared to logseq
I use it just as a simple as possible, instructions on how I setup backups, important thing about container’s config, etc etc. I find it easier to just have a folder “Server” and put each container in a separate note or folder. It’s too much thinking about tags, links, pages and all in logseq, notes seem all over the place.
Yep, now, I initially found the daily journal approach a bit strange, but I use this for work as much as personal stuff, so it actually helps...
My suggestion to your usecase would be to keep a page per "thing" ie server / container / etc and then when you make a change you can just say (on that day's journal page):
'' Setup a backup for [[Server X]] and it's going to [[NAS2]] (for example) ''
Then, on either of those 2 pages you'll automatically see the link back to the journal page, so you'll know when you did it...
I think you can disable the journal approach if it's not useful...
But, the important part is, the files underlying the notes you're making are in plain text with the page name as the filename, whereas with Joplin you could never find the file...
Also, if you modify the file (live) outside of Logseq, it copes with that and refreshes the content onscreen.
And the links are all dynamic... renamed the NAS? Fine, Logseq will reindex all the pages for you...
I would be willing to try it, but the workarounds to get sync on iOS are what makes me not do it