Papa Dragon a partagé un commentaire sur cette publication/conversation

Streams

Sat, 21 Oct 2023 12:37:00 +0200 dernière modification : Mon, 23 Oct 2023 08:47:09 +0200 de Y

Papa Dragon a écrit la publication qui suit Sat, 21 Oct 2023 12:36:57 +0200

Question for all admins, how did you install your @!Streams-based website(s)?

Feel free to add any additional info in the comments!

Traduction pour les francophones:

Question pour les admins, comment avez vous installé votre/vos site(s) basé(s) sur Streams?

Vous pouvez bien sûr donner plus d'infos dans les commentaires!

Options du sondage:

Manuellement, en utilisant les instructions sur le fichier INSTALL.txt du dépôt git
En utilisant l'un des scripts d'installation du dossier 'contrib' du dépôt git
Sur un serveur YunoHost, en utilisant le paquet Streams
En tant qu'application préinstallée proposée par un hébergeur (comme K&T Host)

Manually, using the repo's INSTALL.txt instructions

1 Vote

Using one of the install scripts in the repo's 'contrib' folder

1 Vote

On a YunoHost server, with the Streams package

1 Vote

As a preinstalled app offered by a hosting provider (like K&T Host)

2 Votes

Le sondage est terminé.

Papa Dragon

Sat, 21 Oct 2023 18:26:53 +0200 de CaseLibre

Hum. I can't vote. Did I miss something?

Einer von Vielen

Sat, 21 Oct 2023 18:28:25 +0200 de streams

Using one of the install scripts in the repo's 'contrib' folder

Papa Dragon

Sat, 21 Oct 2023 18:39:03 +0200 de CaseLibre

Me too :)
Soon I will be switching to a YunoHost server, though

lotfi

Sat, 21 Oct 2023 20:29:55 +0200 de Cirtensis

I could vote, but I don't see results.

Papa Dragon

Sat, 21 Oct 2023 20:48:24 +0200 de CaseLibre

Hmm. Something's wrong.

Bill Statler

Sat, 21 Oct 2023 20:52:47 +0200 de Bunny of Doom

My vote is ignored too.

Anyway: I did it manually with INSTALL.txt.

Papa Dragon

Sat, 21 Oct 2023 21:15:11 +0200 de CaseLibre

I'm going to repost the poll on my channel without sharing it on a group, see if it makes a difference.

Luke

Sat, 21 Oct 2023 21:04:14 +0200 de streams

Mine is also ignored. However yunohost.

Papa Dragon

Sun, 22 Oct 2023 17:06:06 +0200 de CaseLibre

Works in dev! I'll try to have this in the Streams package ASAP

Anmol Sharma

Sun, 22 Oct 2023 19:33:44 +0200 de Anmol says

Using #git on top of your #yunohost package.

Mike Macgirvin 🖥️

Sun, 22 Oct 2023 21:20:37 +0200 de Y

@Anmol Sharma That would be preferred. Is there documentation someplace? Because sometimes we'll go a few weeks between releases, and other times a few hours. What would be ideal is if you could just install on Yunohost and get whatever the latest version is, and then be able to update like everybody else.

Papa Dragon

Sun, 22 Oct 2023 23:41:32 +0200 de CaseLibre

YunoHost packages don't really use 'git clone', they would download tarballs for initial install and further upgrades. But of course, if you dowload an archive from a git repo, I assume it's not that difficult to turn it in a local git repo and then handle your updates that way. Maybe you could explain how you do that, @Anmol Sharma.

For the moment I try to update the package as soon as a new release is available. Today, for the first time I used a tarball from a git commit that is still only in dev, I guess I could do that again when required. But of course, I can't guarantee that I'll update the package on a regular basis for years to come. So maybe it could be useful to add an option in the package to turn your install in a git managed one. Like with a daily update script, ability to switch git branches from the YunoHost admin interface, and maybe other things I can't think of right now.

Anmol Sharma

Sun, 22 Oct 2023 23:54:48 +0200 de Anmol says

I tried to implement git for the #hubzilla, #zap and #streams #yunohost packages a long time ago. But they removed it while I was away from yunohost.

Here are the steps I wrote for @RockyIII (rockyiii@huby.infozoo.de)
Please feel to improve it.

So, you need to backup your instance first. Yunohost way is prefered, but you can do it manually too(you just need to backup the /var/www/hubzilla folder and the hubzilla mysql database).

$ yunohost backup create -n hubzilla_version_date --app hubzilla --debug

First move the hubzilla folder.

$ mv /var/www/hubzilla /var/www/hubzilla_backup

Clone the Hubzilla in to the /var/www/.

$ cd /var/www
$ git clone https://framagit.org/hubzilla/core.git hubzilla
$ cd hubzilla
$ util/add_addon_repo https://framagit.org/hubzilla/addons.git hzaddons
$ util/importdoc

Copy your files from the hubzilla_backup to hubzilla.

$ cd /var/www/
$ cp -av hubzilla_backup/.htconfig.php hubzilla/.
$ cp -av hubzilla_bacup/store hubzilla/.
$ cp -av hubzilla_backup/cache hubzilla/.

Give proper rights.

$ cd /var/www/
$ chmod -R o-rwx hubzilla
$ chown -R hubzilla:www-data hubzilla
$ chmod -R 775 hubzilla/store hubzilla/cache

Create a log file.

$ cd /var/www
$ touch hubzilla/php.log

Now it should work. Test it, if everything works you can safely remove /var/www/hubzilla_backup.
If things do not work as expected, you have two options. 1. mv hubzilla_backup to hubzilla(risky as database will be updated to latest version).

Restore with the Yunohost the normal way.

Mike Macgirvin 🖥️

Sun, 22 Oct 2023 23:55:26 +0200 de Y

Downloading an archive doesn't give you any way to access it via git. It sort of needs to start with a git clone instead of a tarball.

Papa Dragon

Mon, 23 Oct 2023 00:44:15 +0200 de CaseLibre

I'll see if I can switch from archive download to git clone for the YunoHost package. That part shouldn't be too difficult. Converting the already installed websites to git repos will be the super fun part.

Anmol Sharma

Mon, 23 Oct 2023 15:59:30 +0200 de Anmol says

I think the yunohost package test would fail if git is used.
You can use a combination of both. Ask during the installation if the user is comfortable with git. (Save the option in the streams settings file for Yunohost)
So we have two ways from here.
1.Streams is updated in normal Yunohost fashion for users who don't want to use git.
2.Users force Yunohost Streams package to be updated with command line, as the package will not show new update until you change the version in manifest (there is force option from command line, I don't know if its there in admin web UI). Or you can update directly with stream admin panel. You will need to find a way to stop the upgrade if new version of php is required. There will be a way to get the php requirement in Streams, you will have to check how Mike will handle this for Streams admin panel. Most likely there will be a warning that the next update will require a php version upgrade. So you will have to catch that and stop the git pull on force upgrade.

And if the user has case 1, then users should not be able to upgrade from the streams admin panel either. The button should be disabled or there should be a warning that the upgrade is not possible because git was not used during installation. I think this check might already be in place.

Other than that, you need to consider how you will handle the transition for users who have already installed the package and are not using git. What default behaviour will you keep for them, git or no git(You have to make sure the Yuno team and your audience are happy. I hope the fun stays.)

The package needs improvements.
There is still no option for postgres for streams like there is for hubzilla, we need to check if LDAP is working again, if fail2ban is working fine with wrong credentials, logrotate needs to be set for the log file and finally the store and cache folder needs to be moved to the /home/yunohost.app folder so that when the core backup is done the users data is not backed up. Users can rsync the data or have the flexibility to choose how the user data is to be backed up.

Papa Dragon

Mon, 23 Oct 2023 16:22:34 +0200 de CaseLibre

Offering a choice between git clone or tarball sounds nice. But I I think it would be a maintenance nightmare. I say you have to choose between the two of them for this package. I never saw a YunoHost package offering such a choice, and I don't feel like writing the first one to do that. No matter how lovely it sounds.

I'll get back to you about the improvements you suggest a little later, as I promised my second son we'd play chess this afternoon :)

Papa Dragon

Mon, 23 Oct 2023 19:31:18 +0200 de CaseLibre

About postgresql I was told this on the YunoHost Apps xmpp chat room:

Allowing user to choose between dB engines seems like an overkill, just use postgresql if support is golden

Since I'm in no way competent when it comes to DB, I'd rather leave it that way.

I tried to workt on LDAP integration a few weeks ago, turns out it was not such a good idea. You'll find more details here. If creating your channels using your LDAP account means not being able to clone them, does not seem to be worth it.

Fail2ban and logrotate are supposed to be configured in the install script, I did not make sure they do actually work.

the store and cache folder needs to be moved to the /home/yunohost.app folder so that when the core backup is done the users data is not backed up.

I would think that saving users data is actually a thing you want to do when backing up a social networking app. What do you mean exactly by "core backup"?