I'm using misskey, outta the box. It's got almost no English-language documentation. Takes a little bit of brainpower (and practice) just to run the bash installer.
#Misskey is a #Node#Typescript application, running on port 3000, and uses #postgresql and #redis for data backend. I'm assuming that the redis does fast cacheing of some sort, not sure what all is there. Also has #nginx set up as a #reverseproxy on port 80, even though the the documentation tells us to expose port 3000 to the world.
That's what I did. I'm assuming that most federation would still work even with port 3000 closed, but it's not worth taking the chance.
The entire application is very fast running and very snazzy looking when it's running all on one box with a good deal of hardware available.
I know that misskey works, and it's a good program, but I want it to be slightly budget-optimized and somewhat containerized so that I can tinker with other containerized applications with the #VPS I already have running.
@mk@p@djsumdog I can understand you both. On one hand, software X can migrate/upgrade its file structure (e.g. "binary format") by itself by running automatically some migration/upgrade script. These scripts can be bound to version numbers (when the upgrade takes place) so the user=admin isn't bothered by it. The "in-place" migration also forces the upgrade on the user=admin.
But it seems like #PostgreSQL seem to follow an other philosophy that says that administrators are the responsible persons and it should be in their full control when the migration/upgrade should take place. So they don't want to force the upgrade on the admin's decision-making progress and let him decide whenever it takes place.
So what would be the solution? A simple script like pg_upgrade.sh that the administrator can manually run or for those people like @mk is that the installer asks "Should pg_upgrade.sh run for your automatically?" and it is done then during upgrade.
Looking for a good read on #postgres . Any books one can recommend for a deeper dive into #postgresql ? Something medium to advanced level but with more practical running examples than the official documentantion? ☺️
Mon collègue DBA/sysadmin a annoncé son départ aujourd'hui... Cela a deux conséquences : - je vais passer une mauvaise semaine, de mauvaise humeur - #jerecrute : un(e) libriste convaincu(e), qui aime #debian, #postgresql, #haproxy, #nginx, #python, #puppet (ou qui tolère puppet en tout cas). et qui aime/support le #télétravail#remote
Pas besoin d'être parfait ou de cocher toutes les cases... (annonce à venir, comme ça je vous laisse un peu de temps pour mettre à jour vos CV ).