Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update infrastructure to use NextJS for frontend #2741

Merged
merged 1 commit into from
Oct 22, 2024
Merged

Update infrastructure to use NextJS for frontend #2741

merged 1 commit into from
Oct 22, 2024

Conversation

blarghmatey
Copy link
Member

What are the relevant tickets?

https://github.com/mitodl/hq/issues/5556

Description (What does it do?)

Now that we are ready to use NextJS as the production frontend service we are removing the references to S3 as the asset origin. This also removes the duplicate Fastly service that was being used for testing and extraneous DNS entries.

How can this be tested?

Run a Pulumi preview and verify that the duplicate DNS and Fastly entries will be deleted and the existing Fastly service will point to NextJS

Now that we are ready to use NextJS as the production frontend service we are removing
the references to S3 as the asset origin. This also removes the duplicate Fastly service
that was being used for testing and extraneous DNS entries.
@feoh feoh merged commit e9b3cc2 into main Oct 22, 2024
4 checks passed
@feoh feoh deleted the nextjs_cleanup branch October 22, 2024 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants