Sign up
Dependencies
Restore
From the project root, run:
dotnet restore
Building
From the project root, run:
dotnet build
Unit testing
From the project root, run:
./run-unit-tests.sh
Publishing
From the project root, run:
./publish.sh
Running
This step requires that the solution has been restored and published (see above). Ensure that docker has access to at least 4GB of RAM for the MSSQL container. Note also that the database takes ~15 seconds to initialise.
From the project root, run:
docker-compose up
Head to http://localhost:5000 in your browser. This will redirect you to https://localhost:5001 and display a warning about an unsafe certifcate. This is because the certifate is self signed and generated during the docker-compose up command. Click on Advanced > Proceed to localhost (unsafe) in chrome or the equivalent in another browser to continue. You should then see a sign up form.
After a user has signed up, check that the user has been successfully added to the database by running the following command while the db container is running:
docker exec -it db /opt/mssql-tools/bin/sqlcmd -U sa -P myPASSWORD123 -d SignUp -Q "SELECT * FROM users;"
Stopping
From the project root, run:
Ctrl+C
docker-compose down
Cleaning
From the project root, run:
./clean.sh
Notes
-
A valid password is a password that has a length inbetween 12 and 32 characters. This makes the password significantly hard to crack and allows users the freedom to enter whichever characters they desire. Complex passwords are still highly recommended. See Password Security: Complexity vs. Length for more information.
-
The script used to create the database and tables used by the app is located at setup.sql. This script gets run as part of
docker-compose up. No manual run is needed. -
A self signed certificate has been used to encrypt sensitive information (email and password) about a user that signs up.