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

Explore install script for datakit #12

Open
tthibo opened this issue May 21, 2019 · 3 comments
Open

Explore install script for datakit #12

tthibo opened this issue May 21, 2019 · 3 comments
Assignees

Comments

@tthibo
Copy link
Member

tthibo commented May 21, 2019

In addition to improving our documentation and creating some intro tutorials, we discussed the possibility of creating an install script (a la https://get.rvm.i).

@zstumgoren
Copy link
Contributor

Datakit is designed to use standard Python package installation techniques (i.e. pip install or pipenv install). So basic installation of the core library and plugins should be straight-forward.

However, the level of complexity associated with configuring an ecosystem of datakit plugins for a particular individual or team can vary depending on the plugins used. @tthibo - Is the goal here to create a higher-level script that can install and help configure a common set of plugins? Or perhaps multiple scripts designed for different user types (e.g. Ruby full stack web developer vs. R data analyst vs. Python data analyst)?

@tthibo
Copy link
Member Author

tthibo commented May 21, 2019

Yep, I was thinking more along the lines of a basic setup for a reasonable running rig. Looking for a way to give folks a quickstart that they can later configure. Perhaps a "common set of plugins" is the best way to start, and then we could always build out different setup scripts for different use cases.

@zstumgoren
Copy link
Contributor

@tthibo Yep. that makes total sense. That was actually the reason behind the datakit-ap repo. Basically a way to minimize some of the pain of installing the ecosystem and configuring it out of the gates. One starting point might be to simply clean up, generalize and open source datakit-ap under a new name. But open to other ideas as well. That plus some related documentation on how to use and customize.

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

3 participants