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
[Configuration] Reading the user's configuration file, if it exists, in developer mode should not be possible #280
Comments
I had to do a history rebase ( then |
…ed only if it doesn't already exist) (#280)
The issues in this ticket now seems to have been fixed. The configuration is now clearly separated between user and developer mode. Please note that, as the history has been rewritten, it is necessary to start from a new populse_mia clone. It is therefore strongly recommended to make a copy of the Once these directories have been saved somewhere, the fresh populse_mia can be cloned from github. If they're not saved somewhere, the configuration will have to be completely redone by hand (which isn't a tragedy, just a waste of time), but especially if personal pipelines and processes have been created, they'll be lost. WARNING! After installing the fresh clone. The management of paths to personal processes was sub-optimal before this ticket. It might be worth modifying by hand the Paths part (end file) of properties_dev_path/dev/properties/process_config.yml (in the case of dev mode, use properties_user_path/usr/properties/process_config.yml in the case of user mode): delete all paths (which are more or less erroneous before this ticket) and keep only the absolute path to the process directory, for example :
I am available to help if problems |
If the configuration file exists in the ~/.populse_mia directory, it is this one that is read in developer mode, whereas in developer mode it should be the populse_mia/properties/config.yml file.
Indeed the interest to have a developer mode and a user mode is to be able to use on the same station, without virtual environment, mia from source and mia from pypi, if one wishes it. The two configurations must be isolated.
The text was updated successfully, but these errors were encountered: