Your team should be proud! You've deployed the site to the cloud, created a database, and made the appropriate updates to get everything connected.
Of course, you typically want to develop locally rather than on a production site in the cloud. As a result, the next goal is to setup local development.
Each member of your team will now clone the project and run it locally. You will use Git and GitHub to clone the project, install any required software, and run the appropriate scripts to start the site.
The template uses the Azure Static Web Apps CLI to emulate Azure Static Web Apps. The Azure Static Web Apps CLI handles integration between the client and Azure Functions running locally on your system, and emulates authentication. When you run the site locally and login, you will be presented with a screen asking you to provide a user ID, username and roles. You can use whatever values you wish for testing locally.
For the local database MongoDB In-Memory Server is used. This means whenever you restart the project any data in the database is removed. If you wish you can install MongoDB locally and update local.settings.json with the appropriate connection string. PLEASE NOTE, for purposes of this workshop, you are NOT required to setup MongoDB locally.
Your team will have successfully completed this goal when everyone can:
- Run the project locally
- Login to the site running locally with a test account
- Create and mark tasks as complete
Your team might find these resources helpful:
To validate you have successfully setup the project locally, walk through the following steps:
- Navigate to http://localhost:4280
- Login to the site to see the list of tasks
- Provide a username and select Login
- Ensure the username displays
- Add a new task and select Add task
- Notice the page updates with the new task
After enabling authentication and logging in via GitHub, the page should look like this:
Once your team has setup the project for local development, it's time to start making changes!