summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPhilip Sargent <philip.sargent@klebos.com>2021-12-05 17:11:12 +0000
committerPhilip Sargent <philip.sargent@klebos.com>2021-12-05 17:11:12 +0000
commit1aef81dccc80be190f999b95e26236867fdbedfa (patch)
tree04368847919c38f206ff638eae912e9626e18316
parent8a43cf7dfb88b622bdd0869990e9a50701d5f771 (diff)
downloadtroggle-1aef81dccc80be190f999b95e26236867fdbedfa.tar.gz
troggle-1aef81dccc80be190f999b95e26236867fdbedfa.tar.bz2
troggle-1aef81dccc80be190f999b95e26236867fdbedfa.zip
testing WSL2 & docm addn
-rw-r--r--README.txt24
1 files changed, 21 insertions, 3 deletions
diff --git a/README.txt b/README.txt
index 6725139..e3bfb74 100644
--- a/README.txt
+++ b/README.txt
@@ -59,6 +59,19 @@ Conventionally on our main master expo server we install everything that we can
[venv description removed - read it in http://expo.survex.com/handbook/troggle/troglaptop.html ]
+Automatic Provisioning and Configuration
+----------------------------------------
+We don't do this - yet.
+We don't even have a bash script.
+The most appropriate configuration tools today (2021) appear to be Bolt or Ansible
+https://puppet.com/docs/bolt/latest/bolt.html (declarative, local)
+https://docs.ansible.com/ansible/latest/user_guide/intro_getting_started.html (procedural, remote)
+https://puppet.com/blog/automating-from-zero-to-something/
+
+We don't need anything for the deploy server itself, but we could do with something for setting
+up test servers quickly to help get newbie developers up to speed faster. But learning a new tool
+creates a barrier in itself. This is one reason most of us don't use Docker.
+
CSS and media files
-------------------
Temporarily we are not using the STATICFILES capability but are instead
@@ -133,13 +146,18 @@ PERMISSIONS
https://linuxize.com/post/usermod-command-in-linux/
sudo usermod -a expo www-data
-adds expo to the www-data group which is what the webserver uses, and thus so the user troggle is acting as when
-running live.
+adds expo to the www-data group which is what the webserver uses, and thus so the user troggle is acting as when running live.
+
+So all the /loser/ .svx files need to have permissions like this (664)
+-rw-rw-r-- expo www-data
+so that the online editing system for SVX files works.
+The same goes for /expoweb/ files, so that "edit this page" works and the New Cave
+and New Entrance forms work.
sudo usermod -a expo expocvs
the expocvs group is used for git & hg
-all the users should bve in this group
+all the users should be in this group
Running a Troggle server with Apache