Not to sound dismissive, but this post is such a perfectly phrased AI prompt. 😂
I’m a computer and open source enthusiast from Toronto, Ontario, Canada.
Not to sound dismissive, but this post is such a perfectly phrased AI prompt. 😂
Are you looking for an SSH client specifically? Given the price tag, you’re likely in iOS/iPadOS, in which case I suggest Shelly: https://apps.apple.com/ca/app/shelly-ssh-client/id989642999 It’s only 5 Canuckistani copecs ($5CAD) one time “tip” to the author to unlock “premium” mode which includes iCloud sync of profiles. Note that keys and passwords are not synced (that’s probably a good thing: keys don’t leave your device).
For a cross-platform option, Termius will do everything you want and more. It is a recurring subscription though. Note that it’s part of the Github student pack, so if you have a university/college email, you can sign up for that and get your pro subscription for free.
I think garbage collection is a thing that needs to be run on a regular basis. If you’re using the community edition of Seafile, you’ll need to shut down its services and run an offline garbage collection. If you get a pro license (I think up to 3 users are free), you can run the garbage collection online, i.e. without shutting down the service.
Have you looked at the mod_sftp for ProFTPd? It seems like ProFTPd is alive and well, despite its official site not supporting HTTPS! It seems like mod_sftp supports most of the SSH/SFTP-specific features, whereas ProFTPd may also offer additional features that complement the mod_sftp module. All in all, probably not a 100% match, and definitely not a drop-in replacement, but at least a seemingly viable/supported alternative?
Python? This will require “specialized hardware” just due to the interpreter overhead taking continuous screenshots of everything you do and indexing/storing them. Why bother implementing something like this using an interpreted language??
The error sounds like your sqlite database file is borked, misplaced or not named correctly. Make sure to shut down Plex on the source Windows machine fully before copying it over. Also make sure the path to the database file is valid - not sure where Plex stores that. Also keep in mind that Linux paths and file names are cAsE SenSiTiVE, so if your db file was named “Plex.db” on Windows, and the Linux version of Plex expects “plex.db” - you will get an error.
Other issues to anticipate related to file/directory naming: library/metadata paths. You may need to redefine/rescan all your media libraries to fix that depending on how Plex handles transitions between platforms that use different path separators (Windows = \ and Linux/macOS = /) and case sensitivity (Windows and macOS = case INsensitive and Linux = case sensitive).
Also consider a DB backup/restore (feature built into Plex) may be a better way to transition vs. just copying the DB file over.
If you’re feeling adventurous, you can download a SQLite browser and take a peek at the Plex DB file. See if there are any red flags like paths to libraries that include Windows specific stuff like drive letters. That will probably break in Linux if just copied over. The backup/restore feature may account for that and actually try to take care of the differences… but that’s just a guess; I never tried this and have no experience with it.
Note: I never bothered to run Plex on anything other than Linux.
P.S. some here suggested using Docker (or Podman - probably better in the long run) to deploy Plex. I strongly recommend that option as well, since it abstracts a lot of the nuts and bolts that you no longer need to care about.