Skip Navigation

Posts
35
Comments
563
Joined
2 yr. ago

  • For it to be, you need a solid paying user base. Which is not the case at hand.

    Very often also at.enterprise level the big money is in training, support and courses rather than in the software licenses per se.

  • I am writing this https://wiki.gardiol.org feel free to take a look then ditch it and go your own way.

    Its a bit of different take to today's trends (docker and such).

  • Thats a good one! But I am not French.

  • Some of you guys are nahive.

    The true and best open source stuff is not developed for profit. Once it is, its only a matter of time because, guess what, software development is never really profitable no matter how much you piss off your user base.

    Don't get me wrong: nothing bad in seeking profit, I do it myself too, I don't live of thin air...

    But true open source projects are not developed by seeking sustainability and profit out of it. I steer away from any such project because it's doomed sooner or later and history is full of those projects.

  • Sport, I run, cycle or swim every day of the week. 1 hour mon-fri and 3-5 hours sat/sun.

    And I went to a sport nutritionist who gave me a diet which makes me eat actually MORE (and much more balanced) than before.

    Lost 15kgs in 6 months while gaining lots of muscle tissue that is heavier than fat.

  • A all my services are behind pam-auth, so nobody unless autheorized can see any subpaths. That fix it for security.

    And that make it that browser will ask you to save password and login for each subdomain... But only once for a subpaths.

    But beside this, is freedom of choice such difficult to grasp? My use cases are not yours, better be free to choose rather than forced, isn't it?

    I do have few subdomains as well, I know perfectly how to automatize them and in fact I do, but I don't like having two ways and specially not just because some Dev don't want to look into supporting subpaths. The number of services not supporting subpaths is the vast minority, so there must be enough people wanting to use them after all. And in all cases, they don't support subpaths because framework don't support them (immich) or because devs don't care (ha).

    Stuff like gitea, gerrit, WordPress, all wiki's I ever tried, arrs, jellyfin, podfetch are just the first that pops into my mind that I use and support subpaths.

  • The service runs as an unpriviledged user, even if, at worst, an intruder would delete or replace the wiki itself. Even the php-fpm behind it runs as that unpriviledged user and is not shared with any other service.

    I doubt an attacker could do anything worse than DoS on the wiki itself.

  • Not really... Your attitude is the problem.

    Sub paths are simpler to deploy: need only one certificate, need only one subdomain.

    In any case you need reverse proxy so security is not the matter here.

    Your use cases are not mine and both ways should always be possible.

    You never need a subpath over a subdomain, nor viceversa, it is (or should) always be a choice.

  • It's a work in progress, but https://wiki.gardiol.org (which is OFC self-hosted)

    Anyway, beefy HP laptop with 32gb ram and Xeon CPU to run all services. 3 RAID-1 (Linux sw raid) usb3 volumes to host all services and data.

    Two isp's: Vodafone FVA 5G (data capped) for general navigation and Fastweb FTTC (low speed but uncapped) for backup access and torrent/Usenet downloads.

    Gentoo Linux all the way and podman, but as much limited as possible: only immich (that's impossible to host on bare metal due to devs questionable choices).

    Services: WebDAV/webcal/etc wiki, more stuff, arrs, immich, podfetch, and a few more.

    All behind nginx reverse proxy.

    99% bare metal.

    Self developed simple dashboard

    External access via ssh tunnels to vps

  • Why are subpaths an a anti pattern?

    Why is taking away choices a problem?

    Everybody has its own usage case, why should we prevent them from using their?

  • Require a subdinain should not be mandatory in 2024.

    Sub paths should be such a basic feature that's ridiculous devs don't even take that into consideration.

    Why? Because a software requiring absolute paths is as old and obsolete as an msdos program, and the only real reason it happens today is... Bad design choices or limited frameworks.

  • My internet speed doesn't allow for this unfortunately. On Usenet I can reach 1mb/sec when lucky. And 6Tb of stuff takes time to find and download again.

  • OK, I installed tdarr and... Well, not impressed. Quite messy, low quality UI and... Paid features. Meh

    Tomorrow will try Unmanic, feels much more refined, I will see.

    Nothing against "paid" in tdarr, just doesn't seems worthwhile given the low quality of the UI.

    I am sure I am judging the book by the cover, but hey, even the Unmanic documentation feels better.

  • I need to encode in something future-proof that can be streamed to a fire stick pro max (whatever its called) without further transcoding possibly.

    Any suggestion in codecs formats and containing formats?

  • Tdarr looks great, but I don't love Foss software which have paid plans attached. Can it be used really for free if I have one server and plan to do all transcoding there?

  • What's this? The link you posted seems broken...

  • Thanks for pointing out! I was thinking to use abs, but requirement for a specific subdomain is a turndown for me.

    Yeah i could, but that would be annoyng as fuck