Agree, if you are running containers on a casual or "just for fun" basis then automatic updates are fine. But the more you or others depend on the service running, the more it makes sense to perform an update manually, when you have time to troubleshoot any problems that may arise. Or, even update on a test setup first to identify issues and then update on your production setup.
earth_walker
joined 4 months ago
You can install, remove and update apps from Software Manager, so familiarizing yourself with that application is probably a good idea. You can customize the theme and behavior of the desktop in System Settings, which is fun.
You know you can just request the desktop site on FB messenger and use it on your phone that way right?
https://www.makeuseof.com/how-to-view-desktop-version-of-any-site-on-mobile/
What are some artists in that vein that you do enjoy?
No problem, your opinion is valid! Do you like other hyperpop or experimental pop artists?
Traefik is powerful and versatile but has a steep learning curve. It also uses code to control its configuration which is a bonus for reliability and documentation as discussed elsewhere ITT. Nginx proxy manager is much simpler and easier to use, may be a good one to get started with, but lacks the advantages of traefik described above. Nginx proxy manager does support SSL cert automation.
Another suggestion for you, I highly recommend specifying a version for the docker image you are using for a container, in the compose file. For example, nextcloud:29.0.1. If you just use :latest, it will pull a new version whenever you redeploy which you may not have tested against your setup, and the version upgrade may even be irreversible, as in the case of nextcloud. This will give you a lot more control over your setup. Just don't forget to update images at reasonable intervals.
Some examples of technologies which follow that paradigm are docker compose, ansible, nixOS and terraform. But it all depends on your workflow.
I use markdown text files which are synced to my nextcloud instance.
This is somewhat tangential to your post, but I think using infrastructure as code and declarative technologies is great for reliability because you aren't just running a bunch of commands until something works, you have the code which tells you exactly how things are set up, and you can version control it to roll back to a working state. The code itself can be a form of documentation in that case.
It might be time for a rewatch of what will soon be "season 1". I liked PSG quite a bit when it came out. The animation is slick and creative, the soundtrack bumps and the humor is very irreverant. It was a pretty offensive and lizard-brained show but as far as I remember it was just kind of generally poking fun. I have a hard time picturing where they will take the new season though as the first one was kind of a hodgepodge with little direction.