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

[IMP] support customization of the custom conf path. #512

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

LoisRForgeFlow
Copy link
Contributor

This allow you to potentially build different configuration files
based on the enviroment you are using.

@ForgeFlow

This allow you to potentially build different configuration files
based on the environment you are using.
Copy link
Contributor

@ap-wtioit ap-wtioit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A test would be nice (test_dotd has a fragment that tests custom/conf.d maybe we could expand this)

                # ``custom/conf.d`` was properly concatenated
                ("grep", "test-conf", "auto/odoo.conf"),

./custom is copied onbuild into /opt/odoo/custom and is chowned to root:odoo. In dev adding additional directories should be fine (if one exports UID, GID properly). but in other environments there could be permission issues with reading custom conf.d that do not belong to odoo uid inside the container.

Can we ignore such permission issues?

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.

None yet

2 participants