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

ln.connect should not write any .env files #847

Open
falexwolf opened this issue Sep 6, 2024 · 1 comment
Open

ln.connect should not write any .env files #847

falexwolf opened this issue Sep 6, 2024 · 1 comment

Comments

@falexwolf
Copy link
Member

While lamin load and ln.setup.load() should keep writing ~/.lamin/current_instance.env, I think that ln.connect() should not persist anything to disk (should not write .env files).

@falexwolf
Copy link
Member Author

falexwolf commented Sep 8, 2024

Can you also add the ability to pass None, @Koncopd

Meaning we enable the same behavior as in R:

import lamindb as ln

ln.connect()  # <-- this populates ln.setup.settings.instance for just this user session from `current_instance.env`; it errors if this file doesn't exit

This is relevant if people prefer to work with auto-connect switched off.

lamin set --auto-connect false

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

No branches or pull requests

1 participant