I use node
as a calculator a lot. It can be dangerous, because it suffers from floating point errors, but it’s generally more powerful than a calculator if you know the Math lib well.
I use node
as a calculator a lot. It can be dangerous, because it suffers from floating point errors, but it’s generally more powerful than a calculator if you know the Math lib well.
I know tmux
is incredibly popular, but a good use case for it that isn’t common is teaching people how to do things in the terminal. You can both be attached to the same tmux session, and both type into the same shell.
degit
is a tool that will check out a git repo (or a specific branch or commit), but not set it up as a git repo. Basically just downloading a specific commit to a directory.
Did you read my post?
It’s faster and has a different feature set. Also it’s written in Node.js, not PHP, so I can integrate it into my Node.js apps.
Neither of the servers you mentioned can work on a flat file system folder, so managing my Jellyfin media wouldn’t even be possible with either of them.
Neither supports file deduplication, encryption at rest, PAM authentication, or .htpasswd authentication.
Both require a database and can only be managed through their web interfaces.
Both of their web interfaces require modern browsers, so wouldn’t be supported on something like a terminal based browser.
Oh, I didn’t answer your encryption question. It doesn’t support both deduplication and encryption at the same time. You can enable them both, but it won’t deduplicate.
It should support B2, since B2 uses the same protocol. If you run into any issues, feel free to file a bug report.
Thanks, I’ll check out Jekyll. If I can use the same templating, that would be great.
I’ve heard Obsidian is really good, but I’ve never used it. I’ll give it a try. :)
I’m going to add support for CardDAV, that way you can use it to sync your contacts. I’m currently working on the Access Control Protocol extension to WebDAV, which is required for CardDAV.
I’d like to eventually support CalDAV too, but that’s harder than CardDAV.
I’d like to also create another web interface with a more modern feature set for use in newer browsers, and even have file share links.
An idea I’ve been floating is creating a way to use .md files and .html templates to create a sort of blog, website, or notebook. Something that would be really easy to manage. Basically throw it up on a server, put some .md files in, and you’ve got a basic website. I’d like to use it to take notes, since editing markdown on a WebDAV share is super simple, and having searchable notes from that would mean I could drop Google Keep.
It’s not really a full fledged web app, but I launched a WebDAV server this year:
https://hub.docker.com/r/sciactive/nephele
I use it for all sorts of things. It’s got some great features that other WebDAV servers are lacking:
It’s incredibly fast compared to most other WebDAV servers, too.
I use it to manage my Jellyfin libraries, as a personal cloud storage, and as a deduplicating backup server. It works well through a reverse proxy too, so I have multiple instances running on my server with different configs.
There’s also a desktop app that uses the same server under the hood to let you transfer and manage files across your network:
I thought this was https://chimeraos.org/ and I’m not sure how I feel about the name clash. Especially since this project started at least two years after Chimera OS did, from what I can find.
I use Immich, and I love it.
ChromeOS is already an operating system for children. Like, literally. Schools use it because it works well and is really easy to use, and runs on very cheap hardware.
Do yourself a favor and download MusicBrainz Picard.
RAID with parity is technically a backup, just a mostly ineffective one. It’s a backup that allows you to recover from exactly one scenario, single (or double) device hardware failure.
But I definitely understand the mantra “RAID is not a backup”. It’s not what most people think of when they say “backup”.
This is good. We need more GUI tools to keep the noobs out of the terminal. Not only because that gives a better impression, but it also protects them from doing a command wrong and really hurting something.
If you want to waste bandwidth downloading the entire commit history, go ahead.