improve publish instructions on key gen etc

Author: bjornregnell

PUBLISH.md

@@ -1,5 +1,7 @@
 # Instruction for repo maintainers
 
+First two sections are preparations only done once for all or once per machine. Last comes what is when actually publishing.
+
 ## Already done once and for all: Setup publication to Sonatype
 
 These instructions have already been followed for this repo by Bjorn Regnell who has claimed the name space se.lth.cs and the artefact id introprog:
@@ -10,6 +12,58 @@ These instructions have already been followed for this repo by Bjorn Regnell who
 
 * New project ticket (requires login to Jira): https://issues.sonatype.org/browse/OSSRH-42634?filter=-2
 
+## Sbt config and GPG Key setup (done once per machine)
+
+Read and adapt these instructions:
+
+* https://www.scala-sbt.org/release/docs/Using-Sonatype.html
+  * Be aware that step 1 was not used, instead the instructions from this link were used to create keys:
+    * https://github.com/scalacenter/sbt-release-early/wiki/How-to-create-a-gpg-key
+
+  * Step 2-4 from above was used. Then after key generation, step 5 should work according to "How to publish" below. See the last parts of this repo's `build.sbt` and these instructions:
+
+Issue commands below one at a time to make files in `~/.sbt/` and key pair in ascii in `~/.sbt/gpg` and publish key in `~/ci-keys` and then copy to `.sbt/gpg` tested on Ubuntu 18.04 using `gpg --version` at 2.2.4. 
+
+```
+cd ~
+mkdir ci-keys 
+chmod -R go-rwx ci-keys
+cd ci-keys
+gpg --homedir . --gen-key
+gpg --homedir . -a --export > pubring.asc
+gpg --homedir . -a --export-secret-keys > secring.asc
+gpg --homedir . --list-key  
+# <copy> the pub hex string e.g E7232FE8B8357EEC786315FE821738D92B63C95F
+gpg --homedir . --keyserver hkp://pool.sks-keyservers.net --send-keys <paste>
+mkdir -p ~/.sbt/gpg
+cd ~/.sbt/gpg
+cp -R ~/ci-keys/* .
+```
+
+After this you should have this these files `~/.sbt/gpg`:
+
+```
+$ cat ~/.sbt/1.0/plugins/gpg.sbt 
+addSbtPlugin("com.jsuereth" % "sbt-pgp" % "1.1.1")
+
+$ cat ~/.sbt/sonatype_credential 
+realm=Sonatype Nexus Repository Manager
+host=oss.sonatype.org
+user=<YOURUSERID>
+password=<YOURPASSWORD>
+
+$ cat ~/.sbt/1.0/sonatype.sbt 
+credentials += Credentials(Path.userHome / ".sbt" / "sonatype_credential")
+
+$ ls ~/.sbt/gpg
+crls.d            private-keys-v1.d  pubring.kbx   secring.asc
+openpgp-revocs.d  pubring.asc        trustdb.gpg
+
+```
+
+Here is some more info on (unnecessary) config that was **NOT** used:
+* https://www.scala-sbt.org/sbt-pgp/usage.html
+
 ## How to publish
 
 1. Build and test locally.
@@ -20,9 +74,9 @@ These instructions have already been followed for this repo by Bjorn Regnell who
   - Publish the jar to the course home page at http://cs.lth.se/lib using  `sh publish-jar.sh`
   - Publish updated docs to the course home page at http://cs.lth.se/api using script `sh publish-doc.sh`
   - Copy the introprog-scalalib/src the workspace subdir at https://github.com/lunduniversity/introprog to enable eclipse project generation with internal dependency of projects using `sh publish-workspace.sh`. Then run `sbt eclipse` IN THAT repo and `sh package.sh` to create `workspace.zip` etc. TODO: For the future it would be **nice** to have another repo introprog-workspace and factor out code to that repo and solve the problem of dependency between latex code and the workspace.
-  - Update the link http://www.cs.lth.se/pgk/lib in typo3 so that it links to the right http://fileadmin.cs.lth.se/pgk/introprog_2.12-NEW.VER.SION.jar
+  - Update the link http://www.cs.lth.se/pgk/lib in typo3 so that it links to the right http://fileadmin.cs.lth.se/pgk/introprog_2.12-x.y.z.jar
 
-3. In `sbt` run `publishedSigned`
+3. In `sbt` run `publishSigned`
 
 4. Log into Sonatype Nexus here: (if the page does not load, clear the browser's cache by pressing Ctrl+F5) https://oss.sonatype.org/#welcome