Merge pull request #229 from iiab/master

sync from iiab/iiab

roles/1-prep/tasks/main.yml

@@ -95,6 +95,12 @@
     dest: /etc/chrony.conf
     backup: no
 
+# Debian 10 "Buster" is apparently enabling AppArmor in 2019:
+# https://wiki.debian.org/AppArmor/Progress
+# https://wiki.debian.org/AppArmor/HowToUse
+# https://packages.debian.org/buster/apparmor
+# Curiously this has NOT stopped IIAB 7.0/master from working on Debian 10
+# pre-releases, during @floydianslips' March 2019 testing anyway!
 - name: Disable AppArmor -- override OS default (ubuntu)
   service:
     name: apparmor

roles/gitea/README.rst

@@ -1,6 +1,6 @@
-=============
+============
 Gitea README
-=============
+============
 
 This Ansible role installs Gitea - a self-hosted Git service written in Go.
 
@@ -9,16 +9,41 @@ Using It
 
 Gitea should be accessible at: http://box/gitea
 
+Gitea repositories can be cloned using either HTTP or SSH. When cloning with 
+HTTP, the clone URL will start with ``http://box.lan/gitea/``. SSH clone URLs 
+start with ``gitea@box.lan``.
+
+Installation and Setup
+----------------------
+
+Simply run ``cd /opt/iiab/iiab`` then ``sudo ./runrole gitea`` to install
+Gitea. After installing, Gitea will be live at http://box/gitea
+
+The first time you access the Gitea web interface, the home page will appear. 
+Clicking on "Register" or "Sign In" in the upper right corner will take you to 
+the setup page. The recommended settings have been configured for you, but you 
+can change them if you want. For example, you may want to change the site title 
+to match the name of your organization.
+
+After finishing the setup process, you will be directed to a page where you can 
+create a user account. The first account created after setting up Gitea will be 
+an admin account. You can also create an admin account from the setup page 
+under "Administrator Account Settings."
+
 Configuration
 -------------
 
-Gitea has been configured to work with MySQL; it can also be used with SQLite or
+Gitea has been configured to work with SQLite; it can also be used with MySQL or
 PostgreSQL. If you want to use it with a different database, change the 
-``DB_TYPE`` property in ``/etc/gitea/app.ini`` [1] and change the line ``After=mysqld.service``
-in ``/etc/systemd/system/gitea.service`` [2] to one of the following:
+``DB_TYPE`` property in ``/etc/gitea/app.ini`` [1] and add one of the following 
+lines to the ``[Unit]`` section of ``/etc/systemd/system/gitea.service`` [2]:
 
-* SQLite: comment it out.
-* Postgres: ``After=postgresql.service``
+* MySQL: ``After=mysqld.service``
+* PostgreSQL: ``After=postgresql.service``
+
+For MySQL and PostgreSQL, you need to specify the server address, the database 
+name, and the user credentials that Gitea will use to access the database. 
+**Make sure the user exists on the database server first.**
 
 [1] Prior to installing Gitea, instead edit: ``/opt/iiab/iiab/roles/gitea/templates/app.ini.j2``
 

roles/gitea/templates/gitea.service.j2

@@ -2,7 +2,6 @@
 Description=Gitea (Git with a cup of tea)
 After=syslog.target
 After=network.target
-After=mysqld.service
 
 [Service]
 # Modify these two values and uncomment them if you have

roles/nodejs/tasks/main.yml

@@ -71,6 +71,10 @@
   # NOT NEC TO TEST FOR is_raspbian_8 OR is_raspbian_9 AS /opt/iiab/iiab/vars/<OS>.yml
   # DEFINES THESE AS SUBSETS OF is_debian_8 OR is_debian_9 (FOR NOW!)
 
+# 2019-03-29: Above works on Debian 10 Buster pre-releases, but fails on Ubuntu
+# 19.04 Beta.  Comment it out for now, and manually run: "apt install npm" then
+# "npm install -g npm@latest" (all *SHOULD* be magically fixed by 2019-04-18 ?)
+
 - name: Install latest Node.js {{ nodejs_version }} which includes /usr/bin/npm (debuntu)
   package:
   #   name: nodejs={{ nodejs_version }}
@@ -127,3 +131,6 @@
 # This May Change: thanks all for running "apt -a list nodejs" on Buster's
 # daily builds @ www.debian.org/devel/debian-installer/ and Disco Dingo (Ubuntu
 # 19.04) https://launchpad.net/ubuntu/+source/nodejs to keep us informed!
+
+# 2019-03-29: Debian 10 Buster & Ubuntu 19.04 pre-releases made the jump
+# thankfully; currently both offer Node.js 10.15.2

vars/ubuntu-19.yml

@@ -23,8 +23,8 @@ apache_log: /var/log/apache2/access.log
 sshd_package: openssh-server
 sshd_service: ssh
 php_version: 7.2
-# "postgresql_version: 10.3" fails (too detailed for /etc/systemd/system/postgresql-iiab.service on Ubuntu 18.04)
-postgresql_version: 10
+# "postgresql_version: 11.2" fails (too detailed for /etc/systemd/system/postgresql-iiab.service on Ubuntu 19.04)
+postgresql_version: 11
 systemd_location: /lib/systemd/system
 # Upgrade Ubuntu 19.x's Calibre 3.39.1+ to very latest
 calibre_via_debs: False