chore: Add Dev Deployment on Netlify and Link it as a Custom Property on the GitHub Repo

[MFarabi619]

We currently don't have a proper dev deployment to share around. We're using preview links like this one which can be out of date and cause mayhem in communication.

See here for an example of something that would be really valuable.

As an aside, consider reaching out to Netlify/Vercel for a sponsorship for team plans. Would really really make our lives easier.

[HasithDeAlwis]

Would this server as a dev deployment? https://cuhacking-portal-test-deployment.netlify.app Its updated each time main is updated

[MFarabi619]

Would this server as a dev deployment? https://cuhacking-portal-test-deployment.netlify.app Its updated each time main is updated

Yes that works, can we rename it to cuhacking-portal-dev.netlify.app?

Since it's updated each time main is updated, might as well just use cuhacking-portal.netlify.app

You also want to make sure it's not indexed on google otherwise it'll steal SEO from your main deployment :laughing: There should be options in Netlify for it.

For future reference, we're going to have:

• cuhacking.ca
• portal.cuhacking.ca
• docs.cuhacking.ca

Memory links will be:

• 2025.cuhacking.ca
• 2025.cuhacking.ca/portal
• 2025.cuhacking.ca/docs

[HasithDeAlwis]

@JowiAoun could you confirm whether or not this PR should be closed? From my understanding, we are migrating to AWS even for our preview deployments.

[JowiAoun]

Production environment should be on AWS. For the dev and previews, it may add more complications to have away from AWS.

Two different providers will bring overhead and complications, because Netlify & Vercel don't allow for containerized deployments, which we need to keep consistency.

I will give AWS a try for all environments, but the free tier instance may or may not be enough to support prod/dev/previews. Closing this until we need to discuss different deployment options again.