Replace use of paulczar/omgwtfssl image in examples#2445
Replace use of paulczar/omgwtfssl image in examples#2445Abhicodeitout wants to merge 4 commits intonextcloud:masterfrom
Conversation
Signed-off-by: Abhishek Kumar Kushwaha <abhithegabbar@gmail.com>
|
@joshtrichards can you review this one !! |
|
While I haven't tested it, it looks okay. A note : Add some documentation around it. I know about several ways of "oneline ssl via random alpine image" long commands, and these tend to confuse people. Use some sort of placeholder like <PUT.DOMAIN.HERE> and maybe add few lines to the docs about it. Overall, it looks good. Will test it as soon as I can. |
|
@tzerber i have just added a section which includes the replacement of the paulczar/omgwtfssl i don't think i have used any domain information . |
Sorry for the late reply, but I was away from the civilization for a while. Recently we started adding additional information in the readme.md / inline on the compose file for any non-nextcloud third party programs providing both links to their documents/manuals and some information on how to use that software in combination with Nextcloud. |
@joshtrichards @tzerber
Summary
I have replaced the outdated
paulczar/omgwtfsslimage used for self-signed certificate generation with a customcert-generatorservice built on Alpine and OpenSSL. The new solution supports environment-based configuration, improving flexibility and maintainability.What was changed
paulczar/omgwtfsslservice fromdocker-compose.ymlcert-generatorservice with:alpineandopensslentrypoint.shscript to read cert parameters from environment variablescertsvolume for use by other services (likenginx-proxy)Why it matters
paulczar/omgwtfsslis no longer maintainedHow to test
cert-generator: