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
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ When you open an issue please provide:
58
58
- version of Postgres
59
59
- smallest possible snippet of code to reproduce the problem
60
60
61
-
You can also follow me [@briancarlson](https://twitter.com/briancarlson)if that's your thing. I try to always announce noteworthy changes & developments with node-postgres on Twitter.
61
+
You can also follow me [@brianc](https://bsky.app/profile/brianc.bsky.social) on bluesky if that's your thing for updates on node-postgres with nearly zero non node-postgres content. My old twitter/x account is no longer used.
62
62
63
63
## Sponsorship :two_hearts:
64
64
@@ -87,11 +87,11 @@ If your change involves breaking backwards compatibility please please point tha
87
87
### Setting up for local development
88
88
89
89
1. Clone the repo
90
-
2. Ensure you have installed libpq-dev in your system.
90
+
2. Ensure you have installed libpq-dev in your system (the native bindings are built in the test process)
91
91
3. From your workspace root run `yarn` and then `yarn lerna bootstrap`
92
-
4. Ensure you have a PostgreSQL instance running with SSL enabled and an empty database for tests
93
-
5. Ensure you have the proper environment variables configured for connecting to the instance
94
-
6. Run `yarn test` to run all the tests
92
+
4. Ensure you have a PostgreSQL instance running with SSL enabled and an empty database for tests. _note: you can skip the tests requring SSL by setting the environment variable `PGTESTNOSSL=1` if you're not changing any SSL related code_.
93
+
5. Ensure you have the proper environment variables configured for connecting to your postgres instance. Using the standard `PG*` environment variables like `PGUSER` and `PGPASSWORD` etc...
0 commit comments