* Add a new section for the 'Create your Server' directions
* Adjust step numbers depending on which cloud provider is selected.
* Add GCP account creation instructions
Screenshots and i18n will wait until the instructions themselves have
been reviewed and finalized.
* Add directions for creating a new VM isntance.
There is still no recommendation for machine type, and i18n won't be
finished until the directions are reviewed and approved by the team
* Specify f1-micro machine type
Looking at Prometheus for some large servers showed that we never get
above a few hundred megabytes in memory usage and don't go anywhere near
the 10 GB of disk space's worth of virtual memory + persistence.
* Re-order instructions to create the firewall rule before the VM
This way there is no separate assignment step
* Format with Prettier
* Respond to code review
Most importantly, removes the recommendation of CoreOS to instead use
the default Debian image.
* Respond to review comments
Use a CSS class to select the correct dropdowns to clear
Rewrite a ternary statement
* Consolidate the GCP-specific instructions in to a single dropdown
* Internationalize new messages
* Revert accidental message change
* Removed unused messages
* Use computed properties for the step numbers
* Make the translation instructions consistent with that of pre-existing messages.
* Replace placeholder assets
* Respond to review comments
* Remove a spurious comment
* Use single quotes in messages
* Select newly added keys
* Add a comment about force rendering
* Use the newest types for express and remove a conflict between multiple
versions of express between the top level node modules and the
metrics_server node modules. Also fix node typing at major version 12
to avoid issues with typing in node 13.
Maintaining consistency with https://github.com/Jigsaw-Code/outline-client/pull/743 as well as with the app logos for both the client and the manager, flip all of the Outline discs so the light side is on the right. I didn't touch a few (such as metrics.png) which are more complicated and would require access to the file in whatever image editor was used to create them.
* Use Prettier to format HTML, CSS, and Markdown files
Currently alalama uses Sublime's built-in formatter while JonathanDCohen uses VS Code. This standardizes us on Prettier and adds formatting to our pre-commit hooks.
pretty-quick has no option to only format changed lines, so this commit will be followed by a format of the src/ directory in order to keep unrelated formatting changes from polluting diffs in upcoming commits.
Code contributors can use the instructions at https://prettier.io/docs/en/editors.html if they'd like to integrate prettier with their editor of choice
* Format html and css files in ui_components
* Fix some html errors found by Prettier
* Correctly internationalize new UI access key placeholder name
* Add back the keyID for non-English languages
This simply replicates the existing messages so we can release the Data
Limits UI without waiting for these strings to be translated.
* Specify that keyId will be a number
