Want newer node.js - #28
Closed
coyhile wants to merge 2 commits into
Closed
Conversation
coyhile
marked this pull request as draft
May 26, 2020 02:18
Author
|
I moved this to a draft; it's going to take more work to get this done. I got the primary working, but the backupServer, etc need more work to use newer restify and newer pg. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This addresses #17 as well as multiple security vulnerabilities in dependencies such as #19, #22, #24, and #24
I'm currently running these changes in production (if you can call it that) with my postgres shards for personal use on base-64-lts@19.4.0 using nodejs-13.11.0 from pkgsrc. In order to test this, I symlinked the
postgresandinitdbbinaries into the postgres path that manatee expects.The sample sitter.json leads me to believe that one should be able to use the system postgres installation directly. I'll put together a second PR to formalize that in the coming days, as
tools/mkdevsitterspostgresql builds all failed somewhere in the guts of the postgres build overlnsemantics.