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!
I also switched from Joplin to Obsidian after about half a year. There's an open-source plugin that lets you self-host a syncing server.
What I found paradoxical is how easy it is to mod and write plugins for Obsidian compared to Joplin. I would've thought that modifying the open-source candidate would've been easier, but nope.
I second obsidian. I was on the verge to jump onto logseq, but found its way of handling notes to be... different. I also felt a dislike of anytype where I don't really have control over my notes. Obsidian clicked with me from the start and felt right. So I went with it, even though it's not FOSS (which is usually a hard requirement from me).
Yeah, I've been on Obsidian before, but self-hosted syncing on iOS is a bit finicky.
I've heard good things about Logseq, but it's certainly a waaay different approach to notes. I'll have to read more about it. Thanks :)
why is it Postgres db…
Why on earth are you using that? Just use WebDAV, you'll only be required to have some WebDAV server such as Nginx and it will sync GB of notes without issues. https://joplinapp.org/help/apps/sync/webdav/ https://medium.com/learn-or-die/build-a-webdav-server-with-nginx-8660a7a7311
I would've NEVER ever moved to Joplin if it wasn't able to sync with WebDAV. I'm not into having a special daemon running on a server for that task, makes zero sense.
This is the way.
Did you know that you can use Joplin on a standard webdav server? Basically it just takes up the space of the data itself. I have it on a Caddy server and works like q charm synching between Windows and Android client
Came here to say just that. The WebDAV synchronization target is great.
Yeah, I'm yet to play around with WebDAV or learning what it actually is haha Will look into it, thanks :)
Yeah the lack of actual .md files is what killed Joplin for me. Obviously not FOSS but there are self hosted options for Obsidian.
Use Nextcloud AIO mastercontainer, set up joplin with Nextcloud sync (which is webdav). Use the builtin backup function in Nextcloud AIO container to backup nextcloud and the files it contains that are your joplin notes (and anything else you use nextcloud for).
I even use Nextcloud for its Gpoddersync app to keep my podcast subs/progress from Antennapod.
Logseq. That is all. (Oh, and syncthing...)
I find their paradigm... different and not entirely sure if I like it yet, need to look into it more :)
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
Oops I thought you were going to be ragging on an early jazz genre.
Connect it to a DAV server and you dont have to learn a new software.
Gotta learn about that DAV thing everyone is talking about ig haha
Can you not just backup the pg txn logs (with periodic full backups, purged in accordance with your needs?). That's a much safer way to approach DBs anyway.
(exclude the online db files from your file system replication)
Why do you need to back up that server data? The great thing about joplin, is that the full content of your notes (and history) is distributed, like a git repo. As long as you have one device left with your notes, everything else can be bootstrapped from there. If your sync server burns down, start a new one and sync your notes to it again.
Genuine question - doesn't this leave you open to loss of data from database corruption or an app failure (or human error, accidentally deleting a bunch of pages, for example)?
I've used "sync as backup" a lot, and run into these kinds of issues (it's my current OneNote "backup" strategy). I'm just not familiar enough with Joplin to know what risks this exposes.
There is a fail-safe switch in settings preventing the deletion of local copy if the remote is empty
True, should've thought of that. Well, at least this gives me a chance to explore and learn alternatives :P
Seconding what others have already said. You should ABSOLUTELY NOT directly back up /var/lib/postgresql if that's what you're doing right now. Instead, use pg_dump: https://www.postgresql.org/docs/current/backup-dump.html
This should also give you smaller and probably more compressible backup sizes.
Notesnook is great. Not yet self-hostable (server is open source), but they are working on it.
I think you need to learn more about how databases work. They don't typically reclaim deleted space automatically for performance reasons. Databases like to write to a single large file they can then index into. Re-writing those files is expensive so left to the DBA (you) to determine when it should be done.
And how are you backing up the database? Just backing up /var/lib/postgres? Or are you doing a pg_dump? If the former then it's possible your backups won't be coherent if you haven't stopped your database and it will contain that full history of deleted stuff. pg_dump would give you just the current data in a way that will apply properly to a new database should you need to restore
You can also consider your backup retention policy. How many backups do you need for how long?
Setup backup hooks with velero and kopia on a HA postres cluster this week. Biggest DB is Lemmy and that shrinks by a factor of 10 using pgdunp with custom archive. Dumping is 100% the way to go!
Similarly I should do this for my sqlite applications, it looks like kopia can't do incremental backups with them and thinking about it, it makes sebse, likely sane reasons you mentioned.
You are right, I should. They are a bit more complicated than I anticipated, and apparently I'm doing everything wrong, haha. I have backups set up to go 2 years back, but I'm checking backblaze occasionally to check, so it shouldn't be an issue. I have two months so far lol Thanks for the write-up :)
I'm going to start developing my own alternative, is there any features that you really need/want?
I was planning on making this self hosted via docker with the option to save to Google drive.
Here's what I would be looking for;
- Decent mobile app (more than happy to pay for this if it's a one time fee)
- Bonus for a OneNote / Evernote style Android widget. Being able to scroll through and quickly select from my most recent notes in the OneNote widget is really helpful.
- WYSIWYG editor on mobile and desktop (why in God's name does every Foss notes app insist I use a markdown language?) with bullet points, numbered lists, bold, italic, underline, strikethrough, and headings.
- Checklists (as in, ability to add checkboxes to notes)
- Ability to create an arbitrarily deep folder structure
- Tags would be nice
- Import from popular apps like OneNote, Evernote, or Joplin is basically essential at this point. A lot of us have way too fucking many notes to move by hand.
Most of those are on the to-do list! I definitely like the Google keep style widget but want better UX when typing out bullet lists.
Thanks for the suggestions
@DichotoDeezNutz @jaykay Saving to a network drive _OTHER_THAN_ proprietary US mega corporations would be essential for me (eg SFTP, WEBDAV)
A mobile client is vital. I use mobile devices 95%
Please don’t follow joplins folder/notes view. It’s so stupid that folders and notes are in different panels on the left. Just make it a normal list.
I like joplin for its simplicity. No bells and whistles like obsidian.
Docker container would be awesome, but I don’t care for Google drive personally :) If you make the notes folder a volume I can bind to that would be great, as long as they’re normal files haha
If you're after some help with the WebDAV part I set it up for myself recently and would be happy to help adapt my stuff to your stack (mine is Apache + compose, but would be about just as easy with anything else). Reply here or DM any time 💯
And good on you for being turned around on your original premise and being so gracious about it in the comments mate 👍
Awesome, thanks! For now I’ll stay on the db without backups. Joplin saves copies to other devices so if something fails, I still have the other devices :)
I recently switched from Joplin to Obsidian for different reasons. I'd prefer something FOSS, but so far I've been happy with the transition. Since it works with plain markdown files, it would fit your use case
I've switched from Obsidian to Joplin actually, cos syncing was a chore and Joplin is more straightforward imo
Joplin server also will use a file based storage instead of the db. And db then is only used for users
I use joplin as i share notes and collaborate with my wife. Obsidian etc dont do that. Id love to be on obsidian as i really like it but sharing notebooks is mandatory
This is why I'm moving to Joplin too
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| Git | Popular version control system, primarily for code |
| HTTP | Hypertext Transfer Protocol, the Web |
| NAS | Network-Attached Storage |
| nginx | Popular HTTP server |
3 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.
[Thread #413 for this sub, first seen 8th Jan 2024, 22:35] [FAQ] [Full list] [Contact] [Source code]