project-template

What happened?

In file: cookiecutter-django/{{cookiecutter.project_slug}}/.pre-commit-config.yaml line number 1:
exclude: 'docs|node_modules|migrations|.git|.tox' using this statement it excludes any file/directory with word 'docs' in it, for example it will exclude:

• ml_docs/
• docs_serializer.py
• docs/
• docs.py

What should've happened instead?

instead it should only exclud

Since there is already PyScaffold 4.1, we should think about when we officially slate PyScaffold 3.* as no longer supported. Maybe we should even be removing the part in the docs mentioning PyScaffold 2.* for Python 2 projects as hopefully no one is starting new Python 2 projects anymore.

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.

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.