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
Copy file name to clipboardExpand all lines: README.md
+36-2
Original file line number
Diff line number
Diff line change
@@ -37,9 +37,43 @@ To build this site:
37
37
- Run `npm run dev`
38
38
- The site will be available in real time via a localhost URL
39
39
40
+
### Generate a self-signed certificate
41
+
42
+
In order to browse with TLS locally, you'll need a certificate. A self-signed certificate is satisfactory for this purpose. Here's how to set one up.
43
+
44
+
Used for development in a local environment (such as on your personal computer). You only need to do this once. If you've already done this for a different project, just copy your existing `localhost_cert.pem` and `localhost_key.pem` files from `~/.ssh` into the root directory of this repo and skip the rest of this step.
45
+
46
+
-[Install mkcert and generate certificate](https://github.com/FiloSottile/mkcert) by running the commands below, in this order:
47
+
```zsh
48
+
cd~/.ssh
49
+
brew install mkcert # replace with another package manager for linux distro
50
+
brew install nss # need to install certutil before running `mkcert -install` so the CA can be automatically installed in Firefox
51
+
52
+
# at this point, open any https website in Firefox before running the below commands
- Copy the new `localhost_cert.pem` and `localhost_key.pem` files to the root directory of this repo
60
+
61
+
The above tutorial is specifically for MacOS machines with `brew` installed. For other \*nix OS's replace the installation step with your preferred package manager (e.g. `apt install mkcert`).
62
+
63
+
### Environment variables
64
+
65
+
Add the following `.env` file to the repo root
66
+
67
+
```ini
68
+
NODE_ENV=stable
69
+
SERVER_ENV=development
70
+
AIRTABLE_SINGULARITY_ACCESS_TOKEN=<entry>
71
+
72
+
```
73
+
40
74
## Updating dependencies
41
75
42
-
Please use `npm ci` in place of `npm i` when not explicitly upgrading dependencies. `npm ci` will only install versions of packages provided in the lockfile, leading to more stability.
76
+
Please use `npm ci` in place of `npm i` when not explicitly upgrading dependencies. `npm ci` will only install versions of packages provided in the lockfile, leading to more stability.
43
77
44
78
Always regression test the site if upgrading packages, as they may contain breaking changes.
45
79
@@ -82,6 +116,6 @@ To better display the components available on the site, their properties, and th
0 commit comments