Skip to content

Conversation

Abhicodeitout
Copy link

@joshtrichards @tzerber

Summary

I have replaced the outdated paulczar/omgwtfssl image used for self-signed certificate generation with a custom cert-generator service built on Alpine and OpenSSL. The new solution supports environment-based configuration, improving flexibility and maintainability.

What was changed

  • Removed paulczar/omgwtfssl service from docker-compose.yml
  • Added a new cert-generator service with:
    • Dockerfile using alpine and openssl
    • entrypoint.sh script to read cert parameters from environment variables
  • Mounted cert output to existing shared certs volume for use by other services (like nginx-proxy)

Why it matters

  • paulczar/omgwtfssl is no longer maintained
  • The new solution is minimal, secure, and customizable
  • Aligns better with modern Docker Compose practices

How to test

  1. Build and run the cert-generator:
    docker compose build cert-generator
    docker compose up cert-generator

Signed-off-by: Abhishek Kumar Kushwaha <abhithegabbar@gmail.com>
@Abhicodeitout
Copy link
Author

@joshtrichards can you review this one !!

@tzerber
Copy link
Contributor

tzerber commented Jul 23, 2025

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.

@Abhicodeitout
Copy link
Author

@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 .
and document updation can you clarify little on that .

@tzerber
Copy link
Contributor

tzerber commented Sep 2, 2025

@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 . and document updation can you clarify little on that .

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants