Changes between Version 11 and Version 12 of how-to/servers/support/gnusocial

Timestamp:

Sep 8, 2017, 1:02:57 AM (8 years ago)

Author:

Steve Revilak

Comment:

admin updates

how-to/servers/support/gnusocial

@@ -7 +7 @@
 ticket:10723 is contains a (somewhat disorganized) hodgepodge of information about gnusocial administrivia
 
-= Administration = 
+= Web Administration = 
 
 The administrative credentials are stored in keyringer.  Look for social.mayfirst.org.
+
+= General deployment and updates =
+
+social's web front end is apache with php5-fpm.  It's the same basic setup we use on moshes.
+
+social's code is stored in a git repository: {{{git://git.mayfirst.org/mfpl/gnusocial}}}.  Branches in this repository are:
+* master - based on the upstream master branch, with no modifications
+* mfpl-master.  A copy of the master branch, with mfpl modifications
+* mfpl-1.1.x.  A copy of the upstream 1.1.x branch, with mfpl modifications
+* mfpl-1.2.x.  A copy of the upstream 1.2.x branch, which we've never used.
+
+We deploy code from tags on the mfpl-master branch.  For example
+{{{
+0 gnusocial@howard:~/social.mayfirst.org/web$ git status
+HEAD detached at social-20170905.1
+
+# social-20170905.1 is a signed tag
+}}}
+
+For updates, the general idea is to
+
+* clone {{{git://git.mayfirst.org/mfpl/gnusocial}}}.  Call this remote `gmo'
+* clone the vendor git repository.  Call this remote `origin'
+* move changes from origin/master -> mfpl-master
+* test.  At the moment, you'll need to set up your own environment for testing.
+* create a signed tag on the commit you'd like to deploy.
+* {{{git push gmo mfpl-master; git push gmo --tags}}}
+* on howard, {{{git fetch gmo}}}, then checkout the tag.
+
+In short, the preferred workflow is to do the work on a test instance, then deploy the changes to howard.
 
 
@@ -70 +100 @@
     ));
 }}}
+
+meteord runs as sv service.  See {{{howard:/etc/sv/meteor}}}