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

Implement 'serve:prod' Script #843

Merged
merged 1 commit into from
Sep 13, 2023
Merged

Implement 'serve:prod' Script #843

merged 1 commit into from
Sep 13, 2023

Conversation

zachary-kent
Copy link
Collaborator

Summary

Implements a 'serve:prod' script, allowing devs to build and test CoursePlan locally for production.

Test Plan

Run npm run serve:prod and check that you can view your production data on CoursePlan.

Implements a 'serve:prod' script, allowing devs to
build and test CoursePlan locally for production.
@zachary-kent zachary-kent requested a review from a team as a code owner August 27, 2023 23:10
@dti-github-bot
Copy link
Member

[diff-counting] Significant lines: 0.

@github-actions
Copy link
Contributor

Visit the preview URL for this PR (updated for commit bf948dc):

https://cornelldti-courseplan-dev--pr843-zak-serve-prod-re7473bi.web.app

(expires Tue, 26 Sep 2023 23:12:25 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 6d4e0437c4559ed895272bbd63991394f1e0e933

@@ -4,6 +4,7 @@
"private": true,
"scripts": {
"serve": "vite",
"serve:prod": "vite --mode production",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible that devs may accidentally modify the production data by spinning up a local build that uses production data?

I don't suspect this happening since only the owner of the data can modify it (i.e the email check in the read/write rules in firestore), but I wanted to ask to make sure its been considered!

Copy link
Collaborator Author

@zachary-kent zachary-kent Sep 6, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah it definitely is possible that someone could nuke their own prod data like this, but they won't be able to modify anyone else's.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome!!

@zachary-kent zachary-kent merged commit e2aee0c into main Sep 13, 2023
@zachary-kent zachary-kent deleted the zak/serve-prod branch September 13, 2023 02:05
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.

3 participants