These might be known issues but here is my experience.
The docker mostly worked for me. There is a typo in the CMD with "bash" at the end of the URL, with that fixed make docker-run let me generate the project files. I then used make docker-shell and ran make setup in my project directory. This failed at git commit because git author identity is unknown. Manually running git config to setup username and email worked, also could add -v ~/.gitconfig:/root/.gitconfig to the docker-run command.
I tried to do everything in the docker because I don't want to install poetry on my machine. This has the disadvantage that the poetry install is lost when exiting the container, but doing a make install worked. I suppose I should create a custom image for my project.
Separate issue but it was unclear how to update generated files like the JSON schema. The README has step 3: edit the schema yaml and step 4: run make test, but I guess there should be a step in between to run make site
These might be known issues but here is my experience.
The docker mostly worked for me. There is a typo in the
CMDwith "bash" at the end of the URL, with that fixedmake docker-runlet me generate the project files. I then usedmake docker-shelland ranmake setupin my project directory. This failed atgit commitbecause git author identity is unknown. Manually runninggit configto setup username and email worked, also could add-v ~/.gitconfig:/root/.gitconfigto thedocker-runcommand.I tried to do everything in the docker because I don't want to install poetry on my machine. This has the disadvantage that the poetry install is lost when exiting the container, but doing a
make installworked. I suppose I should create a custom image for my project.Separate issue but it was unclear how to update generated files like the JSON schema. The README has step 3: edit the schema yaml and step 4: run
make test, but I guess there should be a step in between to runmake site