Improve spin up script to also deploy new dataverse-frontend repo

[pdurbin]

We just created a new repo for frontend code at https://github.com/IQSS/dataverse-frontend

Obviously, our spin up script (ec2-create-instance.sh), doesn't yet know about this new repo.

Let's add a new flag (-f for frontend?) to what's currently documented at https://guides.dataverse.org/en/5.12.1/developers/deployment.html

The code to change in this repo is just the docs above.

The script itself lives in this repo: https://github.com/GlobalDataverseCommunityConsortium/dataverse-ansible and here's the issue for working on the script itself:

• add flag to clone and configure dataverse-frontend repo gdcc/dataverse-ansible#266

[pdurbin]

Related:

• Design and configure a default option for infrastructure and deployment dataverse-frontend#6

[pdurbin]

Related:

• Add version number to bottom right of each page (e.g. v. 5.13 build 1244-79d6e57) dataverse-frontend#12

[pdurbin]

Done! By @donsizemore in this PR:

• react frontend gdcc/dataverse-ansible#278

To enable the new frontend, you flip this to enabled in a local copy of main.yml and pass -g main.yml:

  frontend:
    branch: develop
    enabled: false
    docroot:
      base: /var/www/html
      dir: spa
    nodejs:
      version: 18
    repo: "http://github.com/IQSS/dataverse-frontend"
    srcdir: /tmp/dataverse-frontend

Thanks, @donsizemore! 🎉