Template 'project' : Adding another backend add-on after initial build

[ksuess]

If I add another backend add-on to a project later after the backend is build, the add-on is not installable.
This is because the Zope configuration will never be updated.
The cookiecutter-zope-instance is only applied if instance/etc/zope.ini does not exist.
See

cookieplone-templates/sub/project_settings/{{ cookiecutter.__folder_name }}/backend/Makefile

Lines 60 to 74 in 90ff2fb

	instance/etc/zope.ini: $(BIN_FOLDER)/pip ## Create instance configuration
	@echo "$(GREEN)==> Create instance configuration$(RESET)"
	$(BIN_FOLDER)/pipx run cookiecutter -f --no-input --config-file instance.yaml gh:plone/cookiecutter-zope-instance
	.PHONY: config
	config: instance/etc/zope.ini
	.PHONY: build-dev
	build-dev: config ## Install Plone packages
	@echo "$(GREEN)==> Setup Build$(RESET)"
	$(BIN_FOLDER)/mxdev -c mx.ini
	$(BIN_FOLDER)/uv pip install -r requirements-mxdev.txt
	.PHONY: install
	install: build-dev ## Install Plone

I suggest to run cookiecutter cookiecutter-zope-instance on every make config, not only on initial installation.
There are many possible and easy solutions to do this.

[davisagli]

@ksuess Sounds good to me.