This is related to ticket #1374, and simplifies the steps for local
development environments to have a working login flow for github and
google.
The improvements were configuration for the client id and secret for
google and github via .env vars instead of having to go through setting
up "Social Applications" via the admin interface, and automating the
process for creating google cloud projects in which oauth clients can be
created. Documentation was adjusted to fit.
That was as far as this could be automated given limitations on both
Google Cloud Platform and Github's APIs for creating oauth clients/apps.
The terraform process can be improved if these tickets see some progress
or an API comes about to support this.
Google
https://github.com/hashicorp/terraform-provider-google/issues/16452https://issuetracker.google.com/issues/116182848
Github
https://github.com/integrations/terraform-provider-github/issues/786
This will alliviate the merge conflicts we keep getting by checking this
file into source control.
-----------
Now, when using docker-compose, to re-generate the `styles.css` file,
you can do so locally in the following ways:
1. locally run `yarn build`
2. run `docker compose build`
- Add new setting for oldest version in S3, adjust logic for oldest versions missing docs
- Add VS code workspace files to gitignore
- Change MINIMUM_BOOST_VERSION to reflect reality
