- 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.
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`
