Deploying to the server

Deployment steps

1. If a new database with imported texts needs to be imported: mysql -u <user> -p <database> < YYYYMMDD-deploy.sql
2. If changes are to be introduced on the frontend, locally run a new build of the frontend via ng serve --prod and then deploy the files generated in dist/crow to the production server.

Post-deployment checklist

• Do the PHP versions used during local testing match the production PHP version (see below)?
• https://crow.corporaproject.org/corpus?search=ancillary%20subordinates&op=or&method=word&offset=0
• https://crow.corporaproject.org/corpus?search=ancillary%20subordinates&op=and&method=word&offset=0
• https://crow.corporaproject.org/corpus?search=ancillary%20subordinates&op=or&method=lemma&offset=0
• https://crow.corporaproject.org/corpus/106i_LN_1_CHN_1_F_10207_PRD?search=ancillary%20subordinates&method=lemma
• https://crow.corporaproject.org/corpus?search=ancillary%20subordinates&op=or&method=lemma&offset=0&course=ENGL%20108
• https://crow.corporaproject.org/repository?search=truth
• Sign in as full text user. Verify full text shows.
• Sign in as export user. Verify export can be generated.

PHP version matching

The PHP version used during local development and on the production server should match. There are a few ways to ensure this is the case.

If using lando, set the PHP version in the .lando.yml file:

services:
  my-service:
    type: php:7.2
    via: apache

Second, set the PHP config version in the composer.json file.

    "config": {
        "platform": {
            "php": "7.2.26"
        }
    },

Finally, make sure that the production server also uses the same version.