Getting our hosting environments setup for Human-Connections repo

[sfc-gh-eraigosa]

Is your feature request related to a problem? Please describe.

@yumibyte @cynthialunamaciel as you work through the class you'll be learning some valuable skills that we are going to use to automate the next steps in setting up https://github.com/JusticeInternational/Human-Connection. There are some key take aways that are important to remember from the class:

1. Using the Azure Login (don't forget to switch tenants to justiceinternational when you login.
   
2. A web app is how we'll be deploying our application to Azure.
3. A resource group is a collection of resources, like web apps and virtual machines (VMs).
4. An App Service plan is what runs our web app and manages the billing (our app should run for free).
5. Using GitHub Actions for CI/CD
6. Finally we'll use GitHub packages , PR's and labels to manage all the workflow

Describe the solution you'd like

Since we're using App Service plans we will have at lest 2 sets of apps we will be deploying. 1 for each of the components of the Human Connections app however this can also be 3 apps since we can use the web for testing. There will be 2 environments, a staging and production environment so we can perform testing. The jobs and configuration for the Dockerfile will live in the project-config repository. Here are how i'd like to see the task break down.

Setup neo4j database

• Create a build script for neo4j in script/neo4j folder. This is an adaptation of this configuration and the current project, JusticeInternational/project-config, folders Dockerfile. Use the shell script to clone and build a docker image for the project.
• create a build workflow file for container build and publishing to docker.pkg.github.com
• create a staging workflow file like you did in the exercise
• create a production workflow file like you did in the exercise
• create an environment setup workflow file for the Azure environment like you did in the exercise.

Setup the backend api service

• Create a build script for backend in script/backend folder. This is an adaptation of this configuration and this folder Dockerfile. Use the shell script to clone and build a docker image for the project.
• create a build workflow file for container build and publishing to docker.pkg.github.com
• create a staging workflow file like you did in the exercise
• create a production workflow file like you did in the exercise
• create an environment setup workflow file for the Azure environment like you did in the exercise.

Integration time

• Integrate the configuration values using github secrets to communicate between neo4j and the backend database.

Additional context

Unknowns

There will be lots of learning here, so don't be afraid to ask questions. We still don't know some answers around backup recover, monitoring, and versioning. We'll make new issues along the way to address those issues. We also will need some form of persistent storage answer for the neo4j database /data folder since we'll not want to loose the data we end up loading, so we'll need a separate issue to address that when we're ready.

If someone finishes early we will also need the web app environment when it's ready.

[yumibyte]

I can work on setting up azure for the neo4j database

[sfc-gh-eraigosa]

We have this setup here; https://github.com/JusticeInternational/project-config/tree/stable/config

We may need to refresh this issue. For now I'm moving it to on hold.