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

Dynamically create the service_conf.yaml file by replacing environment variables from .env #3341

Merged

Conversation

gschmutz
Copy link
Contributor

@gschmutz gschmutz commented Nov 11, 2024

What problem does this PR solve?

This pull request implements the feature mentioned in #3322.

Instead of manually having to edit the service_conf.yaml file when changes have been made to .env and mapping it into the docker container at runtime, a template file is used and the values replaced by the environment variables from the .env file when the container is started.

Type of change

  • New Feature (non-breaking change which adds functionality)

@KevinHuSh KevinHuSh added the ci Continue Integration label Nov 12, 2024
Copy link
Contributor

@writinwaters writinwaters left a comment

Choose a reason for hiding this comment

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

Graceful indeed. Many thanks!

@writinwaters
Copy link
Contributor

Also, thanks for the painstaking edits to the README and docs!

@yuzhichang yuzhichang removed the ci Continue Integration label Nov 12, 2024
@yuzhichang
Copy link
Member

The CI is blocked due to unable to connect to ragflow-server. Need to investigate why.

@KevinHuSh KevinHuSh added ci Continue Integration and removed ci Continue Integration labels Nov 12, 2024
@yuzhichang yuzhichang added the ci Continue Integration label Nov 12, 2024
@yuzhichang yuzhichang force-pushed the replace-env-vars-in-service-conf-file branch from d17ef33 to bc14c4a Compare November 12, 2024 14:50
@yuzhichang yuzhichang merged commit 0c95a33 into infiniflow:main Nov 12, 2024
2 checks passed
@yuzhichang
Copy link
Member

Fixed code to pass CI.
Welcome contribution!

@gschmutz
Copy link
Contributor Author

gschmutz commented Nov 14, 2024

@yuzhichang thanks for fixing it, pretty sure it worked when I tested it a few days ago. But I like it better if it is done all in the conf folder.

Will you close the corresponding issue #3322. I have created or should I do it?

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

Successfully merging this pull request may close these issues.

4 participants