qfieldcloud
qfieldcloud copied to clipboard
QF-4641 Deployment path decision for letsencrypt certificates
QFieldCloud build and run in containers extended by feature request to new support automated renewal of certificates by letsencrypt beside the already supported self-singed certificates by mkcert.
The code was handed over to me more or less working regarding the new functionality added. I further tested the certificate creation and automated renewal managed by certbot. I did now mainly test and adapt the development build for (local) dev and deployment build for test and production in the way, that both certificate creation methods can coexist with the same configuration file derived from .env.example as described in the README markdown. The main change from my side is, that the deployer should decide about the certificate setup in the beginning, before continuing with any further build steps. A review is appreciated