Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configurations file added into conf.d or as a secret not being read #119

Closed
szollin opened this issue May 18, 2021 · 2 comments
Closed

Configurations file added into conf.d or as a secret not being read #119

szollin opened this issue May 18, 2021 · 2 comments

Comments

@szollin
Copy link

szollin commented May 18, 2021

When trying to test the Docker version, I tested the conf.d setup for my MOTD as well as setting up opers.conf with a secret. Both were setup following the directions in the README.md file. The MOTD redirection to my custom one failed to be seen and my opers.conf file was never read. In digging through the running container, I found no reference to conf.d in any config file or script. I also found the only secret being checked for is the SSL certificates and that is in the entrypoint.sh script. Can someone check to see if a connection got severed somewhere in the development or if I am doing something wrong.

@szollin
Copy link
Author

szollin commented May 21, 2021

I did some more digging and the config.sh script has references to conf.d and any conf file in /run/secrets. Looks like the issue is that these calls to add the configs are not being placed in inspircd.conf which causes it not to do anything with those files.

@szollin
Copy link
Author

szollin commented Jun 9, 2023

It looks like after a few updates, this is fixed.

@szollin szollin closed this as completed Jun 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant