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.

Sign up for GitHub

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

Jump to bottom

Hardcode CLIENT_CONFIG into installation files #954

Closed
prasadtalasila opened this issue Oct 6, 2024 · 2 comments
Closed

Hardcode CLIENT_CONFIG into installation files #954

prasadtalasila opened this issue Oct 6, 2024 · 2 comments
Labels
enhancement New feature or request
Milestone
Release v0.6.0

Comments

@prasadtalasila
Copy link
Contributor

The CLIENT_CONFIG is a variable in installation configuration. Given that the CLIENT_CONFIG is recommended to be placed in deploy/config/client directory, it is better to hardcode this path into docker compose files. We can reduce one variable from installation.
@prasadtalasila prasadtalasila added the enhancement New feature or request label Oct 6, 2024
@prasadtalasila
Copy link
Contributor Author

The corresponding documentation needs to be updated as well.

@prasadtalasila prasadtalasila added this to the Release v0.6.0 milestone Oct 11, 2024
@prasadtalasila prasadtalasila mentioned this issue Oct 18, 2024
Closed
5 tasks
@prasadtalasila prasadtalasila moved this from Backlog to In progress in Digital Twin as a Service Oct 22, 2024
@prasadtalasila
Copy link
Contributor Author

completed in PR #988

@github-project-automation github-project-automation bot moved this from In progress to Done in Digital Twin as a Service Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
Digital Twin as a Service
Archived in project
Milestone
Release v0.6.0
Development

No branches or pull requests
1 participant
@prasadtalasila