Skip to content

Latest commit

 

History

History
123 lines (84 loc) · 3.58 KB

azure_portal_restore_from_backup.md

File metadata and controls

123 lines (84 loc) · 3.58 KB
Raw
  1. Create VM from backup

  1. Wait until new VM has been created

  1. To access the box we pop the following in our ~.ssh/config
Host hlpwiki-production-clone
HostName hlpwiki-production-clone.cloudapp.net
User bitnami
  1. Now need to adjust the box

a) adjust the port endpoints (they get randomised)

need to be as follows:

b) ensure apache is running (may involve configuring sshd) c) set up agileventures subdomain on gandi DNS

hlp-wiki-production-clone 10800 IN CNAME hlpwiki-production-clone.cloudapp.net.

d) tune the parsoid/mediawiki/apache config

in /home/bitnami/apps/mediawiki/htdocs/LocalSettings.php update the Parsoid URL

## Parsoid service for Visual Editor

$wgVirtualRestConfig['modules']['parsoid'] = array(
        // URL to the Parsoid instance
        // Use port 8142 if you use the Debian package
        'url' => 'https://hlp-wiki-production-clone.agileventures.org:8000',
        // Parsoid "domain", see below (optional)
        'domain' => 'localhost',
        //Parsoid "prefix", see below (optional)
        'prefix' => 'localhost'
);

update sudo nano /etc/mediawiki/parsoid/config.yaml

        mwApis:
        - # This is the only required parameter,
          # the URL of you MediaWiki API endpoint.
          uri: 'https://hlp-wiki-production-clone.agileventures.org/api.php'
          # The "domain" is used for communication with Visual Editor

update nano /etc/mediawiki/parsoid/settings.js

parsoidConfig.setMwApi({ uri: 'https://hlp-wiki-production-clone.agileventures.org/api.php', prefix: ...

update sudo nano /opt/bitnami/apache2/conf/bitnami/bitnami.conf (stop apache before this change)

<VirtualHost *:80>
  DocumentRoot "/opt/bitnami/apache2/htdocs"
  ServerName hlp-wiki-production-clone.agileventures.org
  Redirect permanent / https://hlp-wiki-production-clone.agileventures.org/
</VirtualHost>

<VirtualHost *:8000>
  ProxyPreserveHost On
  ProxyRequests Off
  ServerName hlp-wiki-production-clone.agileventures.org
#  ServerAlias healthylondon.org
  SSLEngine on
  SSLCertificateFile /etc/letsencrypt/live/hlp-wiki-production-clone.agileventures.org/fullchain.pem
  SSLCertificateKeyFile /etc/letsencrypt/live/hlp-wiki-production-clone.agileventures.org/privkey.pem

  ProxyPass / http://localhost:8142/
  ProxyPassReverse / http://localhost:8142/
</VirtualHost>

<VirtualHost _default_:443>
  DocumentRoot "/opt/bitnami/apache2/htdocs"
  ServerName hlp-wiki-production-clone.agileventures.org
  SSLEngine on
  SSLCertificateFile /etc/letsencrypt/live/hlp-wiki-production-clone.agileventures.org/fullchain.pem
  SSLCertificateKeyFile /etc/letsencrypt/live/hlp-wiki-production-clone.agileventures.org/privkey.pem

  <Directory "/opt/bitnami/apache2/htdocs">

e) set up the ssl certs (stop apache first)

sudo certbot certonly --standalone

Notes

Apparently we can upgrade a mediawiki in place

Setting up backups on staging (to mirror the situation on production)