Create auto-deployment scripts for demo server

[Ed McDonagh]

At least with current develop branch deployed to server on successful completion of tests. Possibly another branch/all commits, probably do the same for demo.openrem.org with the master branch.

Useful notes:

• Testing Deployment Using a Staging Site
• Getting to a Production-Ready Deployment
• Automating Deployment with Fabric
• Fabric docs
• Tox docs

[Ed McDonagh]

Tailored fabfile to openrem. Refs #511

→ <<cset 7f294e4da0cd>>

[Ed McDonagh]

Attempting to get current commit from the bitbucket environment variable. Refs #511

→ <<cset 6c95d8a0204b>>

[Ed McDonagh]

Install fabric before trying to use it. Refs #511

→ <<cset 075e34775f03>>

[Ed McDonagh]

Won;t work due to ssh key error. Committing anyway to check if tag comes through. Refs #511

→ <<cset 9a28aeeda7e2>>

[Ed McDonagh]

Testing getting env from os.environ. Refs #511

→ <<cset 56707d307487>>

[Ed McDonagh]

Attempting a straight dollar. Refs #511

→ <<cset ac33a89a02a8>>

[Ed McDonagh]

Maybe need to do this as a 'local' command. Refs #511

→ <<cset 773b99329c22>>

[Ed McDonagh]

Attempt to assign bitbucket environment variable to tox version. Refs #511

→ <<cset 989ef4011761>>

[Ed McDonagh]

Adding in an ssh command with verbosity to see where the ssh is failing. Refs #511

→ <<cset 8d89d10c16a4>>

[Ed McDonagh]

Shell script for updating git on dev.openrem.org. Refs #511

→ <<cset d39124db624d>>

[Ed McDonagh]

Run shell script from tox. Refs #511

→ <<cset 404707c82876>>

[Ed McDonagh]

Quick test to see if we ever get the bitbucket environment variables! Refs #511

→ <<cset 110c00bfd50f>>

[Ed McDonagh]

Moved the fabric command to the pipelines yaml to see if ssh starts working. Refs #511

→ <<cset 20f5c1cb3321>>

[Ed McDonagh]

Generating a clean commit to ask for help with! Refs #511

→ <<cset a841c5a82f27>>

[Ed McDonagh]

testing with environment variable ssh key. Refs #511

→ <<cset 1fbcbf1f5fa8>>

[Ed McDonagh]

Didn't work. Attempting to see if environment variables are expanded. Expecting BB_OPENREM_KEY to be blank in logs. Refs #511

→ <<cset c27a30c03f97>>

[Ed McDonagh]

Added some env variables at 'account' level. refs #511

→ <<cset c6560ae331a0>>

[Ed McDonagh]

Trying with a non-secure key. Refs #511

→ <<cset 78cf8529e060>>

[Ed McDonagh]

Hoping it was the extra carriage returns causing the issue. Refs #511

→ <<cset 205c73b2337c>>

[Ed McDonagh]

Creating ssh key seems to work. Testing with fabfile. Also using real commit hopefully. Refs #511

→ <<cset 0bd62a97b8dc>>

[Ed McDonagh]

Forgot to install fabric. Refs #511

→ <<cset 3d09be30a487>>

[Ed McDonagh]

Hoorah - some success. Migration didn't work as path was wrong. Refs #511

→ <<cset a93866fd3b48>>

[Ed McDonagh]

Corrected path again. Removed test echos. Refs #511

→ <<cset 42cdae73a751>>

[Ed McDonagh]

Split pipelines up to deploy develop and stage branches, but not others. Tidied up tox.ini. Refs #511

→ <<cset 9ca9f33383fc>>

[Ed McDonagh]

Correcting invalid yaml. Strange indenting required! Refs #511. This shouldn't deploy.

→ <<cset 31c7aea8a58c>>

[Ed McDonagh]

Added gunicorn restart. Not yet starting or stopping celery (if this is something we want to do!) Refs #511

→ <<cset 27d758ede32b>>

[Ed McDonagh]

Added gunicorn restart. Not yet starting or stopping celery (if this is something we want to do!) Refs #511

→ <<cset 27d758ede32b>>

[Ed McDonagh]

Adding deploy to testing.openrem.org for any 'stage' branches. Refs #511

→ <<cset e3d45b10dfed>>

[Ed McDonagh]

Hoorah, it works. Just need to add @dplatten's dummy data and give you all ( @tcdewit, @LuukO, @dplatten ) login details.

• Every time develop branch is pushed to bitbucket and passes the tests, the latest commit is checked out to dev.openrem.org and the database is migrated and the webserver is restarted.
• Every time a branch that ends in stage (eg issue1234whichIwantToTestNow-stage) is pushed to bitbucket and passes the tests, that commit is checked out to testing.openrem.org, database is migrated and webserver is restarted.
• Any other branch that gets pushed to bitbucket just gets tested as normal.

I'll also add https certificates when I get a chance.

[Ed McDonagh]

Deleting shell script we won't be using. Refs #511

→ <<cset dd4aba0f8b2a>>

[David Platten]

Would you like me to email you the dummy data?

[Ed McDonagh]

Yes, though if you email me your public ssh key then I can give you access to log into the server...

[David Platten]

E-mail is on the way. I'm not sure I have a public ssh key - any hints on how I'd know?

[Ed McDonagh]

Depends on your ssh client. You may never have generated them. On a linux box, you'll have a .ssh hidden folder in your home directory, and if you do a ssh-keygen you'll create yourself a private/public key pair. I wouldn't normally bother with a pass phrase. Same for bash/ubuntu on Windows 10. PuTTY is a little different. Generally the file we want will be something like id_rsa.pub.

[Ed McDonagh]

Updating changes. Refs or fixes #464, #476, #498, #503, #504, #505, #508, #509, #511

→ <<cset 87ef1ac19991>>

[Ed McDonagh]

@dplatten I've run up demo on the new server too. Does it need any further tweaking? You have the same david login as the other sites.

[David Platten]

@edmcdonagh, I would simplify the CT and radiographic system display names a little otherwise it's good to go. Thanks.