Skip Navigation

Posts
35
Comments
563
Joined
2 yr. ago

  • Using let's encrypt certbot is so easy and automated that I never bothered for wildcards anyway, so.

  • Now the big question is: are you an Arch or a Gentoo lover? Just joking.

    Good job! Keep it up

  • Yeah, i kind of wrote badly. I mean NGINX configuration is simple enough and static enough not to need a dedicated service for my use case. I don't feel the need to mess with NPM. I have a neat folder structure under nginx config so that adding one service is pretty clean and simple and editing one too.

  • As already stated, it's Dokuwiki. I tried a few and this was the best compromise between features and complexity for my needs.

  • One of the risks associated with wildcard SSL certificates is the increased attack surface they introduce. If one subdomain becomes compromised, it opens the door for potential attackers to gain unauthorized access to all subdomains secured under the wildcard certificate. (first google link)

  • I think NPM is useless (in my use-case...) and can get things more messy, but I plan to check on cockpit later on indeed.

    NPM isn't bad in itself, but NGINX configuration is basically static and IMHO don't require a dedicated GUI.

  • Fully agree

  • Yes, you are right, I have updated the information.

  • I have external usb3 and usb-c raid arrays.... You need to buy expensive enclosures, something that cost 100€+ to be safe, then it will work for a long time.

    My older usb3 array (4 disks in a jbod) is almost 7 years old and kicking.

  • Not really, I don't do GPU encoding anyway so can't say first person.

    But everybody says so on all forums so maybe its true.

  • I got an amazon fire stick, all the new ones support av1 and all android devices from A14 must support av1 too.

    On PC vlc plays it just fine too.

  • Indeed, but YMMV and to me quality is still good if source was not a remix but a top quality encoding

  • Some notes: Don't use GPU to reencode you will lose quality.

    Don't worry for long encoding times, specially if the objective is long term storage.

    Power consumption might be significant. I run mine what the sun shine and my photovoltaic picks up the tab.

    And go AV1, open source and seems pretty committed to by the big players. Much more than h265.

  • In my experience, you always gain space savings going av1 from 264 and 265 as well. For me its always been significant savings at the same quality level.

    Ofc YMMV and use a very recent ffmpeg with the best av1 libraries.

  • Go AV1... In my direct experience the space saving is simply amazing at the same quality.

    265 doesn't seems to be the future since all Android are going to support AV1 by mandatory from A14.

  • Its for lucky people without CG-NAT which today means people from USA mostly....

  • Radicale. Setup was a breeze and Just Works Fine. A piece of set and forget software for me.

  • This looks very cool and promising.

    Iove that you can deploy on bare metal, immich doesn't allow that.

    Does it support base-url? I mean can I host it on xxx.mydomain.com/gallery for example?

  • No idea how to put a nice heart emoticon here... But assume I did!