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 work is a prerequisite for #1290 and #1289
- Create an `EmailData` model which holds email counts per
(CommitAuthor, Version).
- Add management command `sync_mailinglist_stats` to query data from the
hyperkitty database and build `EmailData` objects from it
- EmailData.count is calculated between x.x.0 release_dates
- Add button in EmailData admin to trigger task
- Update the `merge_author` method to update EmailData with the Summed
counts per version and delete EmailData which pointed to the
`CommitAuthor` being merged from.
Testing docker-compose. Here are things I noticed.
- `styles.css` seemed to be missing in the local docker-compose
environment, even though it's present in the docker image. With
docker-compose a volume is mounted. The volume points to your git
repository where styles.css is now git-ignored.
Therefore, I am adding steps in the README to build `styles.css`.
@kennethreitz @rbbeeston , is this incorrect? Should the instructions be
different? What method do you use?
- local development: there had been a note to install Python 3.11. Even
though Django containers are running with Python 3.11, it should be
acceptable for the local OS to have the system default of Python 3.10.
They are not directly interacting. Don't modify the system python.
- To view the Users Guide and Contributors Guide, adding variables to
the env.template (and your .env file)
```
STATIC_CONTENT_AWS_ACCESS_KEY_ID=
STATIC_CONTENT_AWS_SECRET_ACCESS_KEY=
STATIC_CONTENT_BUCKET_NAME=
STATIC_CONTENT_REGION=
STATIC_CONTENT_AWS_S3_ENDPOINT_URL=
```
If anyone uses docker-compose and notices the instructions are
incomplete, please comment and/or contribute fixes to the docs.
- Adds functions to retrieve raw events from the Google Calendar API, extract the data we need for those events, and order those events by month for display
- Documents the new env vars
- Adds new setting for the google calendar API url
- Adds `/calendar/` to URLs, which displays the rendered google calendar **but didn't prettify it**
- Adds events to homepage, using the existing template
- Edits to the homepage template to show the events and make the paging arrows work
This includes running containers for mailman-core and mailman-web, both
connecting to the same database used by the boost web site.
The branch proposes a minor refactoring for the shared usage of the
compose-start.sh script, allowing both the boost web server and the mailman-web
server to wait for the db, run migrations, collect assets and run the django
devserver.
