Big pile of updates in order to support rebuilding ingress-models.info #50
Conversation
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
So... a while ago Google Cloud decided to end-of-life the instance the site was running on. By the time I got around to trying to deploy it on a new instance, I discovered that I had been bitten by a pretty severe case of *toolchain rot*. None of the site would build, and the machine that had the scripts I used in the past was no longer in service... So I decided to upgrade and modernize things a bit, and just start over. This necessitated a handful of changes here--some necessary, some more just for quality of life when developing on a newer toolchain - Switch to `webpack` from `grunt` - Move some files to be in more "standard" locations - Add a `Caddyfile` for easy hosting for local development - Switch to `yarn` - Update "Inventory Entities" to actually just be nested `Drawable`s, as I had intended (one TODO down!) - Clean up a couple of the demos to work better - Add a secondary webpack configuration for a "bundled" build (i.e. minified and all) - Update `eslint` rules - Remove the dependency on `es6-promises`
- Use a scene graph approach, instead - I'm starting to suspect that I've gotten something wrong with the Link drawable... - And beyond that, maybe something wrong with having things in a scene graph, too? - I think `viewProject` updates are being cascaded to children, instead of being relative to them? - I think I need to not flatten child drawables on addition?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
So... a while ago Google Cloud decided to end-of-life the instance the site was running on. By the time I got around to trying to deploy it on a new instance, I discovered that I had been bitten by a pretty severe case of toolchain rot. None of the site would build, and the machine that had the scripts I used in the past was no longer in service... So I decided to upgrade and modernize things a bit, and just start over.
This necessitated a handful of changes here--some necessary, some more just for quality of life when developing on a newer toolchain
webpackfromgruntCaddyfilefor easy hosting for local developmentyarnDrawables, as I had intended (one TODO down!)eslintruleses6-promises