Conversation
Notices
-
FYI: !quitterno and gnusocial.no updated with latest from master branch. !qvitter !gnusocial
- mcscx and Hannes like this.
- التنينوكس repeated this.
-
@knuthollund Awesome.
-
@knuthollund @mmn can !qvitter and !gnusocial be updated automatically, just like #WordPress?
-
@dragnucs Could probably write a script which does that, however I'm not confident in letting it go automatically yet. /cc @mmn
-
@dragnucs Not by itself, we don't have such a mechanism.
-
@dragnucs Neither project is at that point yet, but I do believe the future of updating !selfhost ed services is something like #Wordpress's auto-updates.
-
@lnxw48 I was otherwise thinking maybe we should move !GNUsocial into the cloud and autoupdate via the Google Dropboxgram Twitter API, protected by Cloudflare MITM-as-a-service.
-
@mmn LOL. Updating via #git / #hg / #fossil / #bzr / #darcs sort of works for those willing to learn more of the technical side, but to some degree, the tech-clueless WP user is someone we'll eventually need to pull into our world to make !selfhost ing more mainstream.
-
... even if pulling from a repo is what the update process actually does.
-
@knuthollund @mmn It can for example only update fo minor version and notify about a major one.
-
@dragnucs true, but that requires a proper use of tags on the source code. As for now qvitter uses only "master" as a branch. There is no tagging about release versions , major , minors etc. The projects needs more automatically testing and tagging to setup a automatic pull from the sources. (My opinion). /cc @mmn
-
@zash Yeah, @bashrc has been building an apt package!