Selfhosted

39435 readers

6 users here now

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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Joplin alternative needed (lemmy.zip)

submitted 10 months ago* (last edited 10 months ago) by [email protected] to c/[email protected]

67 comments fedilink hide all child comments

Hi guys! I think I'm over Joplin. Don't get me wrong, it's simple, it works, but… why is it Postgres db…. I have the server on a small box with like 250 GB of space and backing it up with kopia to Backblaze with free 10 GB, so I'm a bit storage cautious.

With each snapshot, it seems like a good chunk of the database changes, even when I don't use Joplin that day. That results in kopia backing up those changed files, and backups keep growing. Right now the Joplin database is like 200Mb, BUT when I export the notes from the app… all of them weigh 2Mb… including images. Yes there is versioning of notes, but they shouldn't be that big after one-two months lol.

I know I know, I'm being a bit weird about it, but I'm getting daily notifications about backups and I see how they grow each day.

Anyway, do you have any alternatives that have an app on iOS and on Linux? Or should I just use Apple Notes in the browser? Thanks

EDIT: The answer was easier than I thought. Just don’t back it up, it’s synced which means each device has a copy of it anyway so there is not really need for it, thanks @[email protected] !

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 10 months ago (1 children)

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...

[–] [email protected] 2 points 10 months ago

I would be willing to try it, but the workarounds to get sync on iOS are what makes me not do it