* attempt upgrade over CI
update shadowbox build node version
wild guess
try other image, not holding my breath
switch image back, try no --upgrade? lol
whoops wrong SHA
trying this tip out of hand - will make platform a env var next
apparently buildx is supposed to detect the platform - lets see
find replace yarn w/ npm
fix git hook
cache npm deps
proper lock and enforce engine
licenses are... generated by yarn lmao
some weird leftovers
explode out test workflow jobs
Title Case and check for cache hit
upgrade NPM
check version...
eh, worth a try
reinstall deps for now so we can debug downstream issues
use root bin
fix npm workspace, merge lint w/ setup
HMMM
attempt cache load
fix keys
remove restore-keys
regular install
attempt more "correct" npm approach
annoyingly caching ~/.npm doesn't cache the global npm version
less correct node_module cache, will roll back if doesn't work
er... node 15 :/, restore keys
changing key...?
permission setting so cache can properly hit
separate dependecy permission task
verbose chmod
fix sentry webhook
consistency thing
* print architecture
* attempt amd64-explicit node image
* attempt nodev16 upgrade
* ah, okay, let's try picking this hash
* fix node version reference and npm run clean
* revert untouched files caught in squash
* remove yarn from travis.yml
* testing ci
* npmrc comment, revert one of cis
* Update src/server_manager/web_app/run_gallery_action.sh
Co-authored-by: Vinicius Fortuna <fortuna@users.noreply.github.com>
* Update src/server_manager/web_app/run_action.sh
Co-authored-by: Vinicius Fortuna <fortuna@users.noreply.github.com>
* licenses change
* fix package-lock regression
* fix webpack-dev-server properly
* set install to ci in Dockerfile
* forgot to include the README
* add ci where it makes sense
* delete this part of the README
* missed one
* testing sub-node_modules
* better chmod
* prefer glob
* reset .github/workflows/test.yml
* oops, yarn in ci
* rename everything (#1006)
* Update test.yml
* check_requirements (#1008)
* reqcheck draft
* finish drafting script - need to test and add to hooks
* attempt to roll our own setup...
* remove setup script and rename a couple things
* remove this nightmare lol
* Update release_manager.yml
* Update test.yml
* 'do' -> 'action'
* run -> start
* Update src/shadowbox/docker/build.action.sh
Co-authored-by: Vinicius Fortuna <fortuna@users.noreply.github.com>
* Update README.md
* Update README.md
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
* rename 'action' to action
* add action list to run action itself
* Update src/shadowbox/README.md
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
* Update README.md
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
* Update scripts/run_action.sh
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
* Update src/server_manager/scripts/fill_packaging_opts.sh
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
* style guide fixes
* lower case fixes
* enforce major version
* Update scripts/run_action.sh
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
* Update package.json
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
Co-authored-by: Vinicius Fortuna <fortuna@users.noreply.github.com>
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
* wip
* rename file and remove bogus test
* create file library and add unit tests
oh lol
formatting
* switch to node-tmp
* makes constants screaming case
* missed a 'text'
* this is what i get for trying to use the web editor
* roll back title case
Our UI components are in a mixture of
* Polymer 1.0 style in JS
* Polymer 2.0 style in JS
* Polymer 3.0 style in TS
* Lit-Element 1.0 in JS
* Lit-Element 2.0 in TS
This change migrates all JS to TS, leaving us with slightly less
divergence between component implementations. This change only adds
type annotations and corrects bugs encountered during type checking.
Some notable bugs fixed:
* We were annotating properties "readonly" throughout, but the correct
annotation is "readOnly". However, the effect of this annotation is not
what we thought it was (it actually makes any attempt to set or bind the
property fail silently, even in the constructor), so I've removed most
uses of this annotation.
* Missing imports and dependencies.
* Several instances of type confusion.
Hopefully, migrating to Typescript will make the code easier to
navigate with automated tools, especially for new team members, and will
accelerate subsequent cleanups.
When the free trial period expires, the Outline project is left linked
to an inactive billing account, and all instances are deleted.
Attempting to list the instances associated with a project that lacks
billing results in an HTTP 403. Currently, this results in GCP login
failure, with a generic error message.
This change makes the manager handle this account state gracefully,
taking the user to the billing setup screen, and from there directly
to the server creation screen.
The current code generates names by concatenating integers in a custom
format, with unusual results. For example, 2021-01-12 at 13:01:50 and
2021-11-02 at 01:31:50 are both rendered as "2021112-13150".
This change produces names like "2021-01-12t13-01-50", which is easier
to read (and less likely to collide).
Our translation system requires extra work to support distinct string
with identical content, and in this case there's no need for distinct
strings anyway.
This cuts the GCP server setup time approximately in half, likely
because it avoids multiple calls to "apt update", which
synchronizes all known package repositories.
This PR also updates the underlying Ubuntu image to the latest LTS
release.
