Complex check can be performed here

The proxy (Openresty/Nginx) can check JWT tokens before passing to the API.
It can also query Postgres directly via Lua to perform more complex logic.

We'll need to do some testing to determine the most perfomant means of enforcing authorization.

• These can all be hard-coded initially

• They will need to support i18n eventually

• Signup verification email

• Magic link email

• Lost password email

We need someone to design and program the members dashboard.
That will be the first page members see upon logging in, so its important.

Need to lookup the name. It can enforce WASP top 10 etc.

The ec2 get hit near constantly with break in attempts. We want to reduce the chance of a problem without relying on AWS specific services.

We'll use functions to reduce what would have been 3-4 database calls down to one.

Create Fastify healthcheck in API.

This will require connecting the API to the Postgres instance.
Return 200 ok or most correct status.
This should work through the Swagger interface.

We need to implement unit, functional and e2e test for all code.
We need someone to look look at the recommend test methodologies for each product we use and create an overall testing plan and strategy.

• Sign Up
• Verify Account
• Resend verification
• Sign In
• Sign Out
• Change Password
• Lost password
• Reset password
• Resend reset code

www.izzup.local and api.izzup.local need self-signed certs created in the openresty container.

Developers will need to add /etc/hosts entries for those hostnames, pointing at 127.0.0.1.

It needs to support

• Sign up
• Enter verification code
• Resend verification code
• Sign In
• Lost Password
• Resend lost password code