You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instructions for syncing with the development environment (#622)
* Instructions for syncing with the development environment. [skip-ci]
unee-t/bugzilla-customisation@25329c2
* Add file back to give better idea of what is required from scratch setup
Copy file name to clipboardExpand all lines: README.md
+6-16
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@
7
7
8
8
They are securely managed in AWS's [parameter store](https://ap-southeast-1.console.aws.amazon.com/ec2/v2/home?region=ap-southeast-1#Parameters:sort=Name). The variables are retrieved via [an environment setup script](https://github.com/unee-t/frontend/blob/master/aws-env.dev), which is utilised by `deploy.sh`.
9
9
10
-
For local development, copy`.env.sample` to `.env`. The values of the environment variables can be obtained from other developers via [Unee-T Slack](https://unee-t.slack.com/messages/C6UM93HD2).
10
+
For local development, use`./env-setup.bash` assuming you have been access to the `uneet-dev` development environment.
11
11
12
12
# Deployment
13
13
@@ -78,20 +78,10 @@ Run in browser's developer console:
78
78
79
79
## How do I set up for local development?
80
80
81
-
Assuming `.env` is already setup, you need to populate yours users db, by cross
82
-
referencing an existing user in the Bugzilla backend. For example running in
0 commit comments