So, after a few revisions, it looks like the new "virtual studio" will consist of a set of packages installed with YunoHost and Ansible. This is probably what I'll be starting 2023 with:

Wordpress : Blog & CMS -- hub site. 🆙
PeerTube : Video distribution. 🆙
Misskey, Pixelfed : PR, possibly team communications. 🆙 🆙 (But considering migrating from Misskey to Calckey).
Resource Space : Asset management. 🛠
Nextcloud : Production sources and office documents. 🛠
Collabora : Live online office documents.
Gitea : Software and website sources. 🆙

And possibly:
Galene : Videoconferencing. 🤷‍♂️ Untested.

Also static websites, like
https://lunatics.tv

I have some other stuff installed, but I'm not seeing much use for it. I think I might remove the extras.


#FilmFreedom #VirtualStudio #Infrastructure
Lunatics Production Log – "Somebody has to be crazy enough to go first!"

Ansible and YunoHost are kind of an iffy combination.

YunoHost is based on a "continuous integration" model. So each time you run it, it tries to get the most up-to-date versions of the software. Sometimes this fixes problems, but other times, things break. There isn't a clean "release" or "version" schedule to stick to.

Which is in conflict with the notion of "repeatable installation" that motivated using a configuration management system like Ansible. Which is really closer to what I feel like I need as a DIY-maintainer.

The continuous-integration approach requires a larger risk of unpredictable demand for IT work. Any upgrade can result in breakage that is hard to recover from.

YunoHost provides a through-the-web GUI approach to managing the configuration, which eases the ongoing burden of the work, but it obviously can't eliminate it -- and apps will occasionally break.

And for my needs, YunoHost doesn't cover all the configuration: I still need to get in and make changes to configuration files. Ansible is handy for doing that in a predictable way -- so long as the configuration files don't change much.

I'm not sure there's a solution for this, other than acknowledging that IT work is an ongoing project expense: either in my time, or in money, if I were to pay someone else to do it.
#FilmFreedom #VirtualStudio #Infrastructure #Ansible #YunoHost
And... it bit me. 😫

So, I needed to reinstall Nextcloud...
but my installation is from a few months ago, and YunoHost recently changed from Debian 10 to Debian 11.

It won't let me install the same Nextcloud that it installed a few months ago. Instead, it goes to the upstream source and tries to get the new Nextcloud, which depends on the new YunoHost, which depends on the new Debian.

So... I would have to completely reinstall the YunoHost server in order to get the new version.

But if I did that, the databases and configuration on all other services on this server (including the posts and federation data from this Misskey instance) would be lost. I've even learned that this can interfere with federation if a new server is set up on the same domain.

After a bit of research (just now), I see that, per YunoHost documentation, their approach is to do a dist-upgrade on the Debian 10 system to migrate to Debian 11.

Right, because that never goes wrong... 🤣

Well, I suppose I will try it, but I'm not overly confident this will work.
#Infrastructure
Tiny File Manager

Web based File Manager in PHP, Manage your files efficiently and easily with Tiny File Manager

@TerryHancock Yes, we propose an upgrade mechanism ... because it's not like "reinstalling everything" is a great option, and "being forever on Debian 10" aint great either ... I you really want the old Nextcloud, you can try installing using an older commit though ...