hotfix-for-234b: Digital Ocean NPM Script Fixes #242
Merged
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 PR changes the way that
npm run dev
andnpm run package
work due to differences in our MacOS shell environment and Digital Ocean's environment../@build-ursys.sh
because./
isn't included in the path by default, as it is in our VSCode integrated terminal./@build-ursys.sh
because it was not being run at all, causing a potential failure to load in net graphs because the libraries were not built.See issue #234 for details.
TECHNICAL NOTES
On Digital Ocean running nc-multiplex, the installation instructions call for running
npm run package
once after doing a pull of thenetcreate-itest
repo. This is to ensure that all built libraries are available, asnc-multiplex
does not do it automatically. Up to now,npm run package
did not build the ursys libraries asnpm run dev
does automatically. This can cause URSYS versions to not be available (showing load errors in the javascript console) or cause URSYS versions to be out-of-date.NetCreate makes fairly minimum use of URSYS itself with the exception of the "Comments" addon, but the libraries must be present for the app to load.