project-template

... if maybe we could one day completely go for ConfigUpdater as template systems for setup.cfg. I think it would save us some code and avoid workarounds like this.

Originally posted by @FlorianWilhelm in pyscaffold/pyscaffold#509 (comment)

We use the template just as a structure for the sections, default values and comments, but not do any str

Hi,
the Dockerfile could look like this:

FROM python:3.9-alpine

ARG USER=copier
ARG GROUP=copier
ARG UID=1000
ARG GID=1000

RUN addgroup -g "${GID}" "${GROUP}" && \
    adduser -h /home/"${USER}" -u "${UID}" -G "${GROUP}" -s /bin/bash -D "${USER}"


RUN set -ex; \
    apk add --no-cache --virtual .build-deps \
        gcc \
        musl-dev; \
    apk add --no-cach

Now that Cloud Manager supports Java 11 and lets you configure it using the toolchains plugin

https://docs.adobe.com/content/help/en/experience-manager-cloud-service/onboarding/getting-access/creating-aem-application-project.html#using-java-11

It would be nice if the archetypes takes Java version as a user input and configures the toolchains plugin out of the box.

https://github.com/readthedocs/recommonmark#recommonmark

We should switch to myst: https://github.com/executablebooks/MyST-Parser

If for some reason, the initial bootstrapper fails (network failure, bad cache etc), creation of dune files in the project could get interrupted - the dune files that trigger the on-the-fly dune rules generation. We could

1. Check in those bootstrapping dune files in the templates
   or
2. Ensure, before running, dune build if dune files are missing.

Ideally, we do both.