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

Load configuration explicitly #418

Open
piraz opened this issue Sep 22, 2022 · 0 comments
Open

Load configuration explicitly #418

piraz opened this issue Sep 22, 2022 · 0 comments

Comments

@piraz
Copy link
Contributor

piraz commented Sep 22, 2022

Currently the firenado configuration is being loaded importing the package firenado.conf.

This is a legacy solution since the beginning, besides of being somewhat convenient, it is pretty hash to set up test cases, and make the process of launching an application dependent of the current directory where the firenado command is being executed.

Migrating the firenado configuration load process to be executed explicitly will give us better control of how and when a configuration is set to an application.

We also could design the launchers to reload a configuration without triggering an application restart.

@piraz piraz added this to the Backlog milestone Sep 22, 2022
@piraz piraz self-assigned this Sep 22, 2022
@piraz piraz modified the milestones: Backlog, firenado 0.9.5 Feb 29, 2024
@piraz piraz modified the milestones: firenado 0.9.5, firenado 0.9.6 Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant