maxking / maxking/docker-mailman
[BUG] docker-compose-postorius.yaml is unmaintained
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 278
- Forks
- 121
- PR merge metrics
- No merged PRs in 30d
Description
Tag/version of Container Images
0.4.5
Quack,
First I would like to point out that the doc does not make it clear that docker-compose-postorius.yaml is postorius-only while the other one is postorius+hyperkitty and in fact I chose to use this one to be sure to also get postorius installed, fail.
Anyway, I noticed the example PostgreSQL links use postgres:// which is deprecated, but docker-compose.yaml was updated to the postgresql:// URL.
Also recently sqlalchemy was bumped and the PostgreSQL container too since this verison requires at least PG 11, but docker-compose-postorius.yaml as not updated.
I think that's all but I might have missed other differences.
I'll get back to trying to make this work. Thanks for maintaining these images.
Regards.
\_o<
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare docker-compose-postorius.yaml with docker-compose.yaml, focusing first on the PostgreSQL URL, SQLAlchemy-related version changes, and the PostgreSQL container version. Check the documentation wording for the postorius-only versus postorius+hyperkitty distinction; done means the example is compatible with the current versions and the differences are accurately documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql, python, sqlalchemy
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100