Conversation
Avis
-
Statut de Guillaume (postblue@herds.eu) sur Thursday, 31-Mar-2016 16:54:32 CEST
Guillaume
Is it possible to package !gnusocial for easy install, setup, and update? With the possibility to configure database, daemons and services on install, with post-install hooks, etc?
1. By packaging it and requesting to add it in major distribution repositories. This require a proper versioning and of course, it should be the "stable" branch. 2. By hosting repositories for major distributions, distributing : * nightly builds updated every night like the !prosody trunk packag in their repository.
* stable builds.- ghostDancer et moved to https://mastodon.social/@lohang like this.
-
Statut de #ApocalypseParty (takeshitakenji@gs.kawa-kun.com) sur Thursday, 31-Mar-2016 17:08:38 CEST
#ApocalypseParty
@postblue If you check out the code via git, you can create a local branch and rebase it against whatever upstream branch you want to update to. -
Statut de #ApocalypseParty (takeshitakenji@gs.kawa-kun.com) sur Thursday, 31-Mar-2016 17:08:52 CEST
#ApocalypseParty
@postblue It's fairly safe, as long as you don't allow web access to .git and below. -
Statut de MMN-o ✅⃠ (mmn@social.umeahackerspace.se) sur Thursday, 31-Mar-2016 17:58:24 CEST
MMN-o ✅⃠
@postblue Debian packaging has been attempted by @bob@primatemind.info -
Statut de Guillaume (postblue@herds.eu) sur Thursday, 31-Mar-2016 18:01:45 CEST
Guillaume
@takeshitakenji It's already what I'm doing now, but that's not the point of my statement. -
Statut de Annah (maiyannah@community.highlandarrow.com) sur Thursday, 31-Mar-2016 18:03:28 CEST
Annah
@postblue I've offered to package it for CentOS when they've kind of decided what the stable release should be and other such things. -
Statut de Guillaume (postblue@herds.eu) sur Thursday, 31-Mar-2016 18:03:38 CEST
Guillaume
@takeshitakenji I'm thinking about easy install/configuration/update handled by a package manager, so is it done with web project like #owncloud or #phpmyadmin for those I'm remembering. -
Statut de Guillaume (postblue@herds.eu) sur Thursday, 31-Mar-2016 18:04:45 CEST
Guillaume
@takeshitakenji Maintaining a git branch is far more time consuming than a package manager update. -
Statut de #ApocalypseParty (takeshitakenji@gs.kawa-kun.com) sur Thursday, 31-Mar-2016 18:06:13 CEST
#ApocalypseParty
@postblue Yeah, because 'git rebase upstream/1.2.x' is so time consuming. Right.
A package manager wouldn't alert you to significant, breaking code changes like a rebase would. -
Statut de #ApocalypseParty (takeshitakenji@gs.kawa-kun.com) sur Thursday, 31-Mar-2016 18:07:18 CEST
#ApocalypseParty
@postblue I still feel like server administration GUIs primarily exist to hide complexity from those who fear it. Dolus likes this. -
Statut de Annah (maiyannah@community.highlandarrow.com) sur Thursday, 31-Mar-2016 18:08:26 CEST
Annah
@takeshitakenji @postblue Complexity in anything you wish to secure is a bad thing. -
Statut de #ApocalypseParty (takeshitakenji@gs.kawa-kun.com) sur Thursday, 31-Mar-2016 18:11:21 CEST
#ApocalypseParty
@maiyannah @postblue But hiding the options that promote the strongest security is even worse. -
Statut de Guillaume (postblue@herds.eu) sur Thursday, 31-Mar-2016 18:12:49 CEST
Guillaume
@takeshitakenji I think that it keeps the idealist "install you own instance" moto far away from being reached, because of blatant technical elitism. Most people don't know how to launch an SSH session. But maybe, if they're using a Linux distribution, even a user-friendly one, like for human beeings or so, they might be one day know how to update their system with the used package manager. I don't expect them to learn how to use #git so thet can start a !gnusocial instance. Christel T. likes this. -
Statut de Guillaume (postblue@herds.eu) sur Thursday, 31-Mar-2016 18:13:55 CEST
Guillaume
@takeshitakenj No its not. Learning how #git works is. -
Statut de Guillaume (postblue@herds.eu) sur Thursday, 31-Mar-2016 18:14:26 CEST
Guillaume
@mmn And where are the remains of that project? :D -
Statut de #ApocalypseParty (takeshitakenji@gs.kawa-kun.com) sur Thursday, 31-Mar-2016 18:15:37 CEST
#ApocalypseParty
@postblue I guess it's hard to see how people different from me work with technology, as it's been central to my life since I was a young child. It's not that I don't want those without skills to work with it, but having someone tell them how to act like most commercial software does doesn't sit right with me, either. -
Statut de #ApocalypseParty (takeshitakenji@gs.kawa-kun.com) sur Thursday, 31-Mar-2016 18:16:43 CEST
#ApocalypseParty
@postblue I'm not a fan of discouraging learning, either. https://gs.kawa-kun.com/notice/34285 -
Statut de Annah (maiyannah@community.highlandarrow.com) sur Thursday, 31-Mar-2016 18:20:07 CEST
Annah
@takeshitakenji @postblue That is beside the point, because that is not an issue inherent to GUI programs. -
Statut de Guillaume (postblue@herds.eu) sur Thursday, 31-Mar-2016 18:22:46 CEST
Guillaume
@takeshitakenji That's understandable. It's really hard to disregard what we know and imagine what it's like to start from fairly nothing. People can learn, of course, or so I want to believe. But it takes a lot of time, and we cannot assume that they're intersted in it or that they should be. -
Statut de Guillaume (postblue@herds.eu) sur Thursday, 31-Mar-2016 18:24:53 CEST
Guillaume
@takeshitakenji I support ways of learning that involve habit, use, and practice. Based on the everyday experience. They are the conditions of possibily for having any interest at all in learning something "for fun". -
Statut de Guillaume (postblue@herds.eu) sur Thursday, 31-Mar-2016 18:25:57 CEST
Guillaume
@takeshitakenji But that's a huge debate over the pedagogy in free software communities, and I've not seen much about it. #ApocalypseParty likes this. -
Statut de Verius (verius@community.highlandarrow.com) sur Thursday, 31-Mar-2016 18:27:08 CEST
Verius
@postblue @takeshitakenji IIRC The steps for installation are mostly putting the files under a directory, creating a database and database user and creating a small config.php (this is what the install script does).
Everything except the config.php bit should be pretty simple to automate and the config.php bit could be done with debconf (or related).#ApocalypseParty likes this. -
Statut de #ApocalypseParty (takeshitakenji@gs.kawa-kun.com) sur Thursday, 31-Mar-2016 18:30:24 CEST
#ApocalypseParty
@verius @postblue Pretty much any package manager would be able to do all that. A PKGBUILD in AUR should be very easy, for example. -
Statut de Verius (verius@community.highlandarrow.com) sur Thursday, 31-Mar-2016 18:34:11 CEST
Verius
@takeshitakenji @postblue Yeah, it's all pretty basic stuff. Pick your poison, package managers, ansible, even Docker would work.
Plugins on the other hand...
Then again, separately packaged plugins should work if the config.php has a bit of smarts to include all files in a directory.#ApocalypseParty likes this. -
Statut de Annah (maiyannah@community.highlandarrow.com) sur Thursday, 31-Mar-2016 18:35:49 CEST
Annah
@verius @postblue @takeshitakenji With RPM/YUM it would actually be pretty trivial to include plugins as optional modules provided they don't require anything more than the add plugin line. Or you had some sort of agreed-upon defaults for the additional settings. For instance you could easily package Qvitter to install with Hannes' suggested defaults. -
Statut de Guillaume (postblue@herds.eu) sur Thursday, 31-Mar-2016 18:47:48 CEST
Guillaume
@verius @takeshitakenji I like the way !prosody handles modules: https://prosody.im/doc/installing_modules. Here's a way of packaging them: https://packages.debian.org/jessie-backports/prosody-modules -
Statut de MMN-o ✅⃠ (mmn@social.umeahackerspace.se) sur Thursday, 31-Mar-2016 19:19:43 CEST
MMN-o ✅⃠
@postblue Heh, I'm afraid I don't have a link handy and I'm too lazy to start searching right now! :) -
Statut de Guillaume (postblue@herds.eu) sur Thursday, 31-Mar-2016 20:40:51 CEST
Guillaume
@mmn Don't worry, I'm not in a hurry.