-
Notifications
You must be signed in to change notification settings - Fork 0
Deployment
Alisha Evans edited this page Jan 29, 2024
·
4 revisions
In order to deploy with GA, updated the variables in the staging and production ops files, accordingly.
This option is only for the "webstore" repository. The individual instances will use the Github Actions deployment process.
As of August 18, 2023 only Alisha Evans and Chris Petersen are authorized users on the Scientist-Softserv Vercel team. Teams do not exist on their own. You must have a personal account, and then be added as a member to the team. Each team member is $20/mo. A personal, hobby, account is free.
If another repository in the scientist-softserv github organization needs to be deployed through Vercel, use the steps below.
- An authorized user must log into their vercel account and switch to the Scientist-Softserv team
- From the dashboard press the “Add New” button. In the drop down click “project”
- You should see a section that says “Import Git Repository” with a list of the current repo’s that Vercel has access to
- There’s a line that says “Missing Git repository? Adjust GitHub App Permissions →” Click the “adjust github permissions” link
- A github pop up will appear asking to install vercel
- Scroll your available organizations until you see “scientist-softserv” and click “configure”
- Click “select repositories” and begin typing in the name of the new repo you’d like to connect
- Select the repo and see it now show up in the list in the pop up
- Scroll to the bottom and click “update access”
- Github will send an email to the owners of the scientist-softserv github repo. Ask one of them to authorize the integration
- You will also be redirected to vercel
- Once the integration has been authorized, you should see the new repository in the “Import Git Repository” list, click “Import”
- You should now be on the configuration page. There are only 2 sections that need updating
- Project name: Used to identify your Project on the Dashboard, Vercel CLI, and in the URL of your Deployments.
- Environment variables: add the values from the .env and .env.local files here (you should be able to copy/paste the entire file)
- Once complete, press the “Deploy” button