differentiate quicksetup based on project folder #1901
Conversation
DropD
force-pushed
the
quicksetup-aiida-path
branch
from
9fef0e3 to
eb320df
Compare
Codecov Report
@@ Coverage Diff @@
## develop #1901 +/- ##
===========================================
+ Coverage 66.82% 66.82% +<.01%
===========================================
Files 320 320
Lines 32590 32592 +2
===========================================
+ Hits 21778 21780 +2
Misses 10812 10812
Continue to review full report at Codecov.
|
|
|
||
| # default database user name is aiida_qs_<login-name> | ||
| # default password is random | ||
| dbuser = db_username or 'aiida_qs_' + osuser | ||
| dbuser = db_username or 'aiida_qs_' + osuser + '_' + aiida_base_dir_hash |
There was a problem hiding this comment.
I get that it makes sense to use a different DB for different config folders.
If the DB is already different, do we still need to append the hash to the username?
There was a problem hiding this comment.
In fact the username is just as important: if it already exists (from another config.json), there is no way to know the password stored in the other config.json.
There was a problem hiding this comment.
Ah right, I forgot that the user names are system-wide.
DropD
force-pushed
the
quicksetup-aiida-path
branch
from
eb320df to
8e4c01d
Compare
Problem:
When using quicksetup with a custom location for the .aiida/ config folder, it might try to create and use an existing dbuser with a new password, causing naive use of quicksetup to fail.
Solution:
Add a uuid of the current
AIIDA_PATHfolder to the db user and db name during quicksetup.