If you have a reverse proxy running on the mini pc and handling jellyfin.y.com then there is this plugin which will send the WoL packet to the jellyfin server when a request is sent.
Dragonish
joined 2 years ago
My experience is that ITs role is to manage organizational liability, not helping people. Perhaps i am naive, but i wanted a job in tech so that i could help support other people in doing amazing work. You do get to do that, but it needs to be constantly framed from that point of organizational liability in order to effect any change. Different orgs have different risk appetites and cultures that make that change easier or harder.
tbh i would still start a carrer in tech, i do not want to dissuade you from such. For me i was better able to navigate the day to day bullshit after i learned what they are actually paying me for vs the dream i had in my head.
That has been my experience as well. Signing with SSH keys has been way easier to maintain over time than GPG. Plus you can use the same key to sign that you use for authentication to simplify system setup.
Hosting my own git server on my NAS made my life easier and better due to the new freedoms it offers. Backups are centralized, and I have all the space i need to keep any interesting code safe. I am using forgjeo now and highly recommend it. You can also use other front ends (or none and just ssh/filesystem) but forgjeo gives me artifacts (ie docker registry), code search, LFS, and more. With my own git server, my local filesystem only has what I am working on recently (or as my workstation space allows). My home folder has a folder for each version control system (git, pijul, svn). Inside of these i have 2 sub folders: /
Some examples of different domains are: open, work, personal, dragonish. I do not separate what forge or remote service in the filesystem, this is a persona boundary.
I use git remote names and branches in each repo to handle what software forge and any upstream/maintainers i need to work with. As an example my work repos only get pushed to my work server (ie, only 1 git remote named origin set to my work's server), but my open ones will go to forgjeo and github (i setup 2 git remotes, origin and github. origin in this domain goes to my forgjeo). If i have a need i go into some more git branching strategy which I do find has helped me over my life, but I think I am overthinking this post now! keep it all simple enough for what your needs are.
I am loving the new release cadence!
Welcome! Without buying more enclosures and increasing the number of drives you can access at one time, you will need to partition your files based on your own use case and maintain an index so that you easily can retrieve the right drive when you need to access data. Perhaps you get a drive for each year. Perhaps images go to one and video to another. perhaps you split on the file name. For an index, this can be as simple as labeling the drives and putting them on your shelf. As mentioned by others, there are software solutions for indexing file metadata as well.
If you buy more enclosures you can use MergerFS or another union file system to bring both disks together and provide a single view while using ext4 for each drive. This allows you to easily remove a single drive and plug it into another basic linux distro, but you will not get any data striping or other protections. So if 1 drive dies, you will loose whatever data was stored on that disk. Because of that, I advise you to still think about partitioning your files even if you union them so that you understand your failure scope.
my understanding is that terms of service would be helpful but not needed if someone trued to sue because you blocked access to the site. I would not expect ToS for a site like you are explaining, but if it did it would say "the web admin will ban you if you are naughty, you have been warned"
For privacy policy i think what you wrote to give us context is near perfect. Explain how your app stores data, be specific about encryption at rest and in motion. If your app is designed to hold name, email address, billing info you should highlight that in your policy. including a (monitored) contact email for questions would be nice, but not needed imo unless you are storing PII
Well you know if only they were wealthy enough to become a vegan in the first place they could buy the good looking carcasses the mean Vegans are making them eat! /s
I am a fan of structurizer and the C4 model in general.
I would use a single .dsl file and add the relationships and entities as you discover them. You can apply tags , and then write filtered views to only show specific tags for sub systems or workflows that a user will follow.
you can pair this with markdown/text notes that reference the png files of the views that structurizer will output.
view more: next ›
i like Taskjuggler, but it may not check all your boxes. specifically there is no kanban or issue tracker built in. It has very basic note capability, so i combine it with markdown files to keep a list of issues, risks, dependencies and references associated with the large projects we are working on. I use a kanban vscode plugin which uses Markdown front matter to set the status and next action date. Taskjuggler has a learning curve, as it is text based and the files that define your projects are stored in source control and need to be transpiled into html reports. It can track time granularly with the bookings feature, although tbh i have never had a need to use that, the basic scheduling has given me a good enough for my need view of resource allocation.