Bugs are of two types - known (found during testing by Distro maintainer) and unknown.
Fixed release fixes known bugs before pushing packages.
It is following the standard development life cycle.
Bugs are of two types - known (found during testing by Distro maintainer) and unknown.
Fixed release fixes known bugs before pushing packages.
It is following the standard development life cycle.
Wayland or X11?
Just to reiterate the same point - in fixed release, a package version is not released until all known issues are resolved.
At no point, it is end user responsibility to bother checking anything before installing a new version.
taking any action required no matter the os
This is not really true for fixed release distros. I can’t remember when was the last time I had to read through the release note before Ubuntu version upgrade, or upgrading any package.
The only reason the menace is can’t be weed out because both local politicians and cops get their cut from these type of Business. So, if you shut down one, 4 more open up next day.
India has a huge pool of English speaking educated young people with no access to decent paying jobs after college. These scam centers offer them easy money.
Rule of Thumb: if your use case is not satisfied by your current Distro, then move to the one that does.
Arch or rolling release distros are great if you want latest version of software/packages as soon as possible. Downside is you need to put more effort/time to maintain it by yourself.
On the other hand, fixed release distros (e.g. Debian) doesn’t offer latest packages immediately. But, given that packages are tested for distro release, so you will have a more stable (in relative term) system for yourself with minimal effort.
I used to like rolling release distros on my college days as I had plenty of time back then. Now, I’m settled on fixed release ditro as it suits my current use case.
Reverse proxy is not specifically for exposing a containerised service on internet, it also helps to enable SSL for all services via single reverse proxy on LAN.
If you want to expose a container based service just for yourself over internet, you can -
If you have static IP4 or IPV6 - Setup Wireguard VPN on your homelab/server, and wireguard client on client devices[1].
If you are behind NAT or CGNAT - either Cloudflared Tunnel[2] or Tailscale[3].
In either scenarios, you need to setup firewall of your server to allow connection from LAN to port of your docker container/services. By default you should set your firewall to block all incoming request from anywhere except LAN.
I’m personally using Cloudflared Tunnel, but planning to migrate to Tailscale.
[1] https://www.digitalocean.com/community/tutorials/how-to-set-up-wireguard-on-ubuntu-20-04
[2] https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/
AdGuardHome is also self-hosted and does have this feature.
Actually in my cases, I have to block Facebook on all of my devices, but want to allow it for rest of my family members. So, I know its possible in AdGuardHome.
https://github.com/AdguardTeam/AdGuardHome
For which self-hosted app? Invidious?
Unless you are routing traffic through a VPN.
That’s correct. Thanks for the correction.
Also, checkout https://selfh.st/apps/
“Requires to create an account” for what exactly? I’m a long term Ubuntu user without any Ubuntu one account.
Ubuntu Core, to be specific.
Ubuntu.
Why? - I guess I’m too lazy for distro hopping now :(
Besides, this was the 1st Linux distro I tried back in 2005. After the usual ditro hopping phase was over, I settled on it; somehow (irrespective of snap and other controversies) I feel at home.
It’s an open source product, in case you have concern about possibility of malicious code embedded within it.
At least there is no such indication so far from Mozilla :(
Are you families with the term “Regression testing”?