It has the benefit that the container can’t start before the mount point is up without any additional scripts or kludges, so no race conditions or surprise behaviour. Using fstab can’t provide that guarantee. The other option is Autofs but it’s messier to configure and may not ship out of the box on modern distros.
This is a fresh install as about 10 minutes ago so using the :latest tag which I believe is the v 2.4.8 build. Signing up is possible and I was able to create my user account so that’s a good start at least. :)
fstab will do it, but the more important question is, what do you want to happen when it doesn’t mount properly? Do you want the system to fail to boot? Do you want navidrome to not run?
But man, I’ll be able to amend all those TODO items that have been accumulating of the last 12 months and fix all those issues while rebuilding my raid.
I mean that’s only if my GITs aren’t hijacked during the ransomware attack.
And I mean, I’ll probably just push the same config to my server and let it on its merry way again.
Well, based on advice of Samsy, take a backup of home-server network to a NAS on your home-network. (I do home that your server-segment and your home-segment are two seperated networks, no?) Or better, set up your NAS at a friend’s house (and require MFA or a hardware security-key to access it remotely)
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
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 :)
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.
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
Amazing! Have wanted something like this for years, currently use raindrop but not fully, very hesitant of locking myself in. This looks very promising.
I’m very curious… Why do you feel locked in by raindrop? I like that it can regularly upload exports to my Google drive and I can Always download them as html and csv.
It’s 2024, avoid Proxmox and safe yourself a LOT of headaches down the line.
You most likely don’t need Proxmox and its pseudo-open-source bullshit. My suggestion is to simply with with Debian 12 + LXD/LXC, it runs VMs and containers very well. Proxmox ships with an old kernel that is so mangled and twisted that they shouldn’t even be calling it a Linux kernel. Also their management daemons and other internal shenanigans will delay your boot and crash your systems under certain circumstances.
What I would suggest you to use use instead is LXD/Incus.
LXD/Incus provides a management and automation layer that really makes things work smoothly - essentially what Proxmox does but properly done. With Incus you can create clusters, download, manage and create OS images, run backups and restores, bootstrap things with cloud-init, move containers and VMs between servers (even live sometimes).
Another big advantage is the fact that it provides a unified experience to deal with both containers and VMs, no need to learn two different tools / APIs as the same commands and options will be used to manage both. Even profiles defining storage, network resources and other policies can be shared and applied across both containers and VMs.
I draw your attention to containers (not docker), LXC containers because for most people full virtualization isn’t even required. In a small homelab if you can have containers that behave like full operating systems (minus the kernel) including persistence, VMs might not be required. Either way LXD/Incus will allow for both and you can easily mix and match and use what you require for each use case.
For eg. I virtualize the official HomeAssistant image with LXD because we all know how hard is to get that thing running, however my NAS / Samba shares are just a LXD Debian 12 container with Samba4, Nginx and FileBrowser. Sames goes for torrent client that has its own container. Some other service I’ve exposed to the internet also runs a full VM for isolation.
Like Proxmox, LXD/Incus isn’t about replacing existing virtualization techniques such as QEMU, KVM and libvirt, it is about augmenting them so they become easier to manage at scale and overall more efficient. I can guarantee you that most people running Proxmox today it today will eventually move to Incus and never look back. It woks way better, true open-source, no bugs, no BS licenses and way less overhead.
I do regular snapshots of my containers live and sometimes restore them, no issues there. De-duplication and incremental features are (mostly) provided by the storage backend, if you use BTRFS or ZFS for your storage pool every container will be a volume that you can snapshot, rollback, export at any time. LXD also provides tools to make those operations: documentation.ubuntu.com/lxd/…/instances_backup/
create clusters, download, manage and create OS images, run backups and restores, bootstrap things with cloud-init, move containers and VMs between servers (even live sometimes).
provides a unified experience to deal with both containers and VMs, no need to learn two different tools / APIs as the same commands and options will be used to manage both. Even profiles defining storage, network resources and other policies can be shared and applied across both containers and VMs.
Your comment is wrong in a few ways and suggests using a LXC which is way slower than docker or podman and lacks the easy setup.
Proxmox is good because it makes it easy to create VMs and setup least access. It also has as new of kernel as stable Debian so no, its not terribly out of date.
If you want to suggest that someone install Debian + Docker compose that would make more sense. This isn’t a good setup for more advanced setups and it doesn’t allow for a not of flexibility.
This was a discussion about management solutions such as Proxmox and LXD and NOT about containerization technologies like Docker or LXC. Also Proxmox uses the Proxmox VE Kernel that is derived from Ubuntu.
Your comment makes no sense whatsoever. I’m not even sure you know the difference between LXD and LXC…
I’ve been on Proxmox for 6 or so months with very few issues and have found it to work well in my instance, I do appreciate seeing another alternative and learning about it too! I very specifically like Proxmox as it gives me an actual IP on my router’s subnet for my machines such as Home Assistant. So instead of the 192.168.122.1 it rolls a nice 192.168.1.X/24 IP which fits my range which makes it easier for me to direct my outside traffic to it. Does this also do this? Based on your screenshots, maybe not, IDK.
it gives me an actual IP on my router’s subnet for my machines
Yes you configure LXD/Incus’ networking to use a bridge and it will simply delegate the task to your router instead of proving IPs itself. One of my nodes actually runs the two setups at the same time, I’ve a bunch of containers on an internal range and then my Home Assistant VM getting an IP from my router.
Thanks for the link! I’ve been running Proxmox for years now without any of the issues like the previous commenter mentioned. Not that they don’t exist, just that I haven’t hit them. I really like Proxmox but love hearing about alternatives. One day I might get bored and want to set things up new with a different stack and anything that’s more free/open is better in my book.
Games from that time were actually running mostly in your browser. Meaning that the host, for example Miniclip served you the JavaScript and other files of the game which were then executed locally. So technically you could archive those games as long as you can load them up at least once initially.
If you logged and saved all the files the first one requested you could potentially make it work. You could manually change of the file paths in the html if you only doing a few of them. There’s only like 10 or so paths that would need to be modified. The PHP ones are likely harder to make work as php is a server side language and you don’t likely have easy access to PHP server and everything that goes with it.
Anyway thanks for the link to to mynoise.net. It looks like a well designed, carefully crafted website.
It’s an open source solution designed to scale to what the web was originally designed for and excels at. Documents. Specifically hyperlinked documents or webpages. You can’t reasonably expect an archival service to archive something that is by definition not static like an interactive web app.
selfhosted
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.