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

DataJoint CLI / launcher script #940

Open
ixcat opened this issue Aug 9, 2021 · 0 comments
Open

DataJoint CLI / launcher script #940

ixcat opened this issue Aug 9, 2021 · 0 comments
Assignees
Labels
Milestone

Comments

@ixcat
Copy link
Contributor

ixcat commented Aug 9, 2021

Feature Request

Problem

Often, a user wants to quickly check on something in a pipeline, etc. without using a 'full' pipeline environment with pipeline code, dependencies, etc. In these cases, often the workflow is:

  • start datajoint
  • set auth configuration
  • connect
  • create virtual modules
  • perform specific task desired

It would be nice to provide a simple utility to quickly launch a connected datajoint session with appropriate schemas loaded
as virtual modules for these cases. Potentially this could be designed in a future-proof way for managing other common DataJoint related things (e.g. create pipeline, change password, setup external, launch UI etc)

Requirements

  • cli utility to launch a connected datajoint session with virtual modules loaded

Justification

see 'Problem'

Alternative Considerations

see 'Problem'

Additional Research and Context

Created a basic script to this end for personal use available here: https://github.com/ixcat/djwip/blob/master/djwip/ixcat/djcli/dj.py

synopsis:

$ dj -h
usage: dj [-u user] [-p password] [-h host] [-s db:schema ...]

-u/-p/-h should be straightforward; -s will map the database schema named db to the schema virtual module named schema e.g. -s ixcat_subject:subject to map the ixcat_subject database schema to a virtual module bound to the variable schema within the resulting interpreter.

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

Successfully merging a pull request may close this issue.

4 participants