yavsc/Dockerfile.backend

# Utilisation de l'image globale pour le build et l'exécution
FROM pazof/yavsc-build-env:debian13-dotnet10-android36-jdk21-v4 AS build-env
WORKDIR /src

# 1. Copie de la solution
COPY . .
RUN dotnet workload restore
# 4. Restauration des dépendances pour tous les projets
RUN dotnet restore
# 6. Compilation du serveur Web principal
RUN dotnet build src/Yavsc.Org/Yavsc.Org.csproj -c Release --no-restore -clp:ErrorsOnly

# 7. Publication de l'artefact Yavsc.Org pour l'image runtime (Dockerfile.runtime).
#    Copie depuis /app/publish/Yavsc.Org/ via --from=build-env. Les appsettings
#    ne sont PAS publiés ici : fournis au runtime via BuildKit secret mount ou
#    volume docker-compose.
RUN mkdir -p /app/publish
RUN dotnet publish src/Yavsc.Org/Yavsc.Org.csproj -c Release --no-build -o /app/publish/Yavsc.Org

# Définition du répertoire d'exécution par défaut
CMD ["bash"]
contributing+compose: clarify 'machine vierge' criterion for Jalon 0 Make explicit what was implicit: 'docker compose up' is not expected to start everything on a bare host. Yavsc.Org (web) requires an HTTPS signing certificate for IdentityServer8 in Production mode, and the volume mount /etc/letsencrypt:/etc/letsencrypt:ro is the documented way to supply it. Two related changes: - CONTRIBUTING.md, 'docker compose up' section: spell out that db + api + blogs start cleanly on a bare host, web fails with the documented IdentityServer error, and that the difference between 'vierge' and 'configured' is exactly the cert volume. - docker-compose.yaml, web service: expand the commented volumes block to point at the same error message and reference the 'HTTPS en production' section in CONTRIBUTING.md, so an operator reading the compose file knows what to uncomment and where to look. 2026-06-27 17:38:08 +01:00			`# Utilisation de l'image globale pour le build et l'exécution`
simpler, better, faster, stronger 2026-10-11 06:27:13 +01:00			`FROM pazof/yavsc-build-env:debian13-dotnet10-android36-jdk21-v4 AS build-env`
Dockerfiles ... 2026-06-07 09:01:21 +01:00			`WORKDIR /src`

			`# 1. Copie de la solution`
			`COPY . .`
simpler, better, faster, stronger 2026-10-11 06:27:13 +01:00			`RUN dotnet workload restore`
Dockerfiles ... 2026-06-07 09:01:21 +01:00			`# 4. Restauration des dépendances pour tous les projets`
			`RUN dotnet restore`
			`# 6. Compilation du serveur Web principal`
			`RUN dotnet build src/Yavsc.Org/Yavsc.Org.csproj -c Release --no-restore -clp:ErrorsOnly`

docker: publish Yavsc.Org / Api / Blogs artifacts to /app/publish Add a 'dotnet publish' step at the end of both Dockerfiles so the runtime images (Dockerfile.runtime / .blogs / .api) can COPY the published output via --from=build-env. Before this commit, the Dockerfiles only ran 'dotnet build' and ended with CMD ["bash"] — i.e. they were pure build-env images with no consumable artifact for runtime use. Dockerfile publishes Yavsc.Org, Yavsc.Api and Yavsc.Blogs (used by docker-publish-android.yml which extracts the APK). Dockerfile.backend publishes Yavsc.Org only (used by docker-publish-backend.yml for the pazof/yavsc production image). Appsettings are NOT published: they are supplied at runtime via BuildKit --mount=type=secret (see Dockerfile.runtime in the next commits) or via a docker-compose volume. 2026-06-27 16:12:16 +01:00			`# 7. Publication de l'artefact Yavsc.Org pour l'image runtime (Dockerfile.runtime).`
			`# Copie depuis /app/publish/Yavsc.Org/ via --from=build-env. Les appsettings`
			`# ne sont PAS publiés ici : fournis au runtime via BuildKit secret mount ou`
			`# volume docker-compose.`
			`RUN mkdir -p /app/publish`
			`RUN dotnet publish src/Yavsc.Org/Yavsc.Org.csproj -c Release --no-build -o /app/publish/Yavsc.Org`

Dockerfiles ... 2026-06-07 09:01:21 +01:00			`# Définition du répertoire d'exécution par défaut`
			`CMD ["bash"]`