From 8086a9de03b718d1df2906680c6c86adb2293114 Mon Sep 17 00:00:00 2001 From: Alan Orth Date: Thu, 28 Sep 2017 12:00:49 +0300 Subject: [PATCH] Update notes for CGIAR Library migration --- content/post/cgiar-library-migration.md | 9 +++++---- public/cgiar-library-migration/index.html | 15 ++++++++------- public/sitemap.xml | 8 ++++---- 3 files changed, 17 insertions(+), 15 deletions(-) diff --git a/content/post/cgiar-library-migration.md b/content/post/cgiar-library-migration.md index 3b79fb765..caf74ce59 100644 --- a/content/post/cgiar-library-migration.md +++ b/content/post/cgiar-library-migration.md @@ -152,16 +152,17 @@ $ for item in 10947-latest/*.zip; do dspace packager -r -u -t AIP -e aorth@mjanj I had been regenerated the `sitebndl.zip` file on the CGIAR Library server and sent it to the Handle.net admins but they said that there were mismatches between the public and private keys, which I suspect is due to `make-handle-config` not being very flexible. After discussing our scenario with the Handle.net admins they said we actually don't need to send an updated `sitebndl.zip` for this type of change, and the above `config.dct` edits are all that is required. I guess they just did something on their end by setting the authoritative IP address for the 10947 prefix to be the same as ours... -- [ ] Update DNS records: +- [x] Update DNS records: - CNAME: cgspace.cgiar.org - [x] Re-deploy DSpace from freshly built `5_x-prod` branch - [x] Merge `cgiar-library` branch to `master` and re-run ansible nginx templates - [x] Run system updates and reboot server -- [ ] Switch to Let's Encrypt HTTPS certificates (after DNS is updated and server isn't busy): +- [x] Switch to Let's Encrypt HTTPS certificates (after DNS is updated and server isn't busy): ``` -$ sudo systemctl stop tomcat7 -$ ./letsencrypt-auto certonly --standalone -d library.cgiar.org +$ sudo systemctl stop nginx +$ /opt/certbot-auto certonly --standalone -d library.cgiar.org +$ sudo systemctl start nginx ``` ## Troubleshooting diff --git a/public/cgiar-library-migration/index.html b/public/cgiar-library-migration/index.html index ec5e048d7..4978c6d96 100644 --- a/public/cgiar-library-migration/index.html +++ b/public/cgiar-library-migration/index.html @@ -13,7 +13,7 @@ - + @@ -37,9 +37,9 @@ "@type": "BlogPosting", "headline": "CGIAR Library Migration", "url": "https://alanorth.github.io/cgspace-notes/cgiar-library-migration/", - "wordCount": "1273", + "wordCount": "1278", "datePublished": "2017-09-18T16:38:35+03:00", - "dateModified": "2017-09-28T10:23:37+03:00", + "dateModified": "2017-09-28T11:54:26+03:00", "author": { "@type": "Person", "name": "Alan Orth" @@ -271,7 +271,7 @@ $ for item in 10568-93760/ITEM@10947-465*; do dspace packager -r -f -u -t AIP -e

I had been regenerated the sitebndl.zip file on the CGIAR Library server and sent it to the Handle.net admins but they said that there were mismatches between the public and private keys, which I suspect is due to make-handle-config not being very flexible. After discussing our scenario with the Handle.net admins they said we actually don’t need to send an updated sitebndl.zip for this type of change, and the above config.dct edits are all that is required. I guess they just did something on their end by setting the authoritative IP address for the 10947 prefix to be the same as ours…