Add a Dockerfile and publish a Docker image of the starter project on Docker Hub
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 35/100
- Issue-Typ
- Feature
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- docker, docker-compose, github-actions, php
- Bereich
- devops, infrastructure
Rechercherichtung
First resolve the listed decisions about the Docker Hub namespace, PHP versions, image type, and database; the work is also gated on the project requiring PHP 8.2. Read the README and project setup requirements, then add the Dockerfile, .dockerignore, docker-compose.yml, and .github/workflows/docker.yml described in the issue. Verify that docker compose up serves the home page and php qt install:demo runs, then confirm the release workflow publishes version and latest tags without baking in secrets.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Summary
Let users run a new Quantum project with Docker, and publish an image of it on Docker Hub with every release. The repository has no Docker files today. This is planned for 3.2.0, which raises the minimum PHP version to 8.2, so the image starts from PHP 8.2.
Why
Starting a Quantum project needs PHP 8.2 or newer (the minimum of 3.2.0), Composer and several extensions (pdo, curl, json, simplexml, fileinfo, openssl, bcmath, plus dom and zip for some features). An image gives a working setup in one command, on any machine, without installing PHP.
Scope
Files to add to this repository:
Dockerfile: PHP 8.2 on Apache, the extensions above, Composer, the document root set topublic/,mod_rewriteon, and write access tologs/,cache/andruntime/. The.envis read at run time, and no secret is stored in the image..dockerignore.docker-compose.yml: the app, a database, and Redis as an option..github/workflows/docker.yml: build and push the image to Docker Hub when a release tag is published, for amd64 and arm64.- A short section in
README.mdon how to run it.
Two kinds of image are possible: a runtime image where the project is mounted or created with composer create-project quantum/project, and a ready image that already contains a created project and starts a working app. The first one comes first; the second is a thin layer on top of it.
To decide before the work starts
- the Docker Hub namespace and repository, and who owns them
- the PHP versions to publish, from 8.2 up
- which kind of image comes first
- which database the compose file starts with
The access token and the account name are stored as the repository secrets DOCKERHUB_TOKEN and DOCKERHUB_USERNAME by the maintainer.
Order
The work starts after the project requires PHP 8.2 (3.2.0), because the image must run the version the project supports.
Out of scope
- Changes to the framework repository.
- Tags and releases: they are cut by the maintainer, and the workflow only reacts to a published tag.
Acceptance criteria
docker compose upstarts the project, and the home page answers- the image runs
php qtcommands, includinginstall:demo - no secret is baked into the image
- a published release tag pushes the image to Docker Hub with the version tag and
latest - the README explains how to run it
- Vorherrschende Sprache
- PHP
- Sterne
- 49
- Forks
- 20
- Ø Merge
- 16 Min.
- Gemergte PRs (30 T.)
- 9
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus quantum-php/project
-
demo good first issue templates
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 45/100
quantum-php/project#195 ·
Alle Issues in quantum-php/project
Ähnliche Issues
-
35-feedback
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug good first issue
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
quantum-php/framework#692 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 70/100
ajeetraina/awesome-docker-sbx#559 ·
-
PHP 8.6 supportOffen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
-
Saisie des adressesOffen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
pantaflex44/Tiquettes#116 · 1 Kommentar ·