Create an Azure Web data service to your monopoly database (created in lab 7) using the Monopoly data service as a model. Creating Web data services is a bit trickly so you’ll reimplement a copy of the sample as follows.

1. On GitHub, fork the sample Monopoly data service repo (for details on how to do this, see Forking a repository). Notes:

   • Give your forked version of the repo a unique name and plan to maintain it as a stand-alone repo, separate from your standard cs262 repo. It will be easier to implement the CI/CD for your Web service this way.
   • Review the contents of the repo, noting the following:
     • README.md — This documents the sample data service; try it out using the browser.
     • src/monopolyService.ts — This script implements the REST data service.
     • scripts/test-cli.http — This file lists the curl commands demoed in class.
     • src/monopolyDirect.ts — This script implements the direct-to-PostgreSQL access for the Monopoly game data demoed in class.
     • .github/workflows/. — Azure Webservices automatically (re)builds the CI/CD scripts in this sub-directory.

2. On Azure, in the list of App Services, Create a new “Web App” and configure it as follows.

   1. Basics
      • Subscription/Resource Group: Use your free student account and your existing resources group.
      • Name: Allow the system to give your service a unique name (e.g., the sample monopoly service URL).
      • Runtime stack: Choose a Node-based stack that’s compatible with the service settings (e.g., version 22).
      • Pricing plan: Choose a free pricing plan (e.g., “Free F1 (shared infrastructure)”).
      Leave the other settings as is; we’ll configure CI/CD after the service is created.
   
   
   2. Review + create the app.

3. On Azure, in your new app service, do the following:

   1. Under Deployment Center→Settings:
      • Choose CI/CD GitHub deployment.
      • Authorize access to your GitHub account by following the GitHub login procedure and being sure to “Grant” access to any GitHub organization that holds your Web app repo.
      • Enter your (forked) GitHub service repo details.
      Be sure to “Save” these settings. This will create a GitHub workflow file in your service repo (in .github/workflows/.) that will automatically deploy your service to Azure whenever you push changes to the main branch of your service repo.
   
   
   2. Under Settings→Environment variables, add separate key-value pairs for your Azure PostgreSQL database:
      • DB_SERVER — See the “Endpoint” name in your PostgreSQL database instance (e.g., cs262.postgres.database.azure.com).
      • DB_PORT — For PostgreSQL this is always 5432.
      • DB_USER — See the PostgreSQL administrator login (e.g., cs262).
      • DB_PASSWORD — Hopefully, you remember this!
      • DB_DATABASE — See the “Databases” page (e.g., postgres).
      Be sure to apply the settings. Note that this approach allows us to keep these (sensitive) values out of our (public) GitHub repo.

   Restart the App service to apply these changes.

4. On Azure PostgreSQL, do the following:

   1. Under Settings→Server parameters, set the value of require_secure_transport to “OFF”.

   Restart the PostgreSQL service to apply this change.

Make sure that your service is running (n.b., you can the URL in the Azure web app “Overview” page) and that it provides all the API endpoints listed in the sample service README. Finally, update your README.md file to link your service URL.

For grading purposes, do the following.

• Push the following into a cs262/lab09/your-service-fork sub-directory in your standard course repo:
  • A copy of your updated README.md file, which should include a hyperlink to the root of your running data service on Azure.
  • A copy of your service application code module (i.e., monopolyService.ts).
  • A copy of the workflow script created by Azure in your service repo (e.g., .github/workflows/master_cs262.yml).
  Keep your service in place because you’ll upgrade it as part of the homework.

You should actively participate in your team’s retrospective and planning session.