-
Notifications
You must be signed in to change notification settings - Fork 5
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
Research & Write Polykey Usecases in Wiki #2
Comments
https://github.com/MatrixAI/js-polykey/wiki/Secrets-Management @scottmmorris we just reviewed 3. task involving the developer, there are some things that need to be developed for the CLI to support that usecase we wrote down. @Zachaccino for the 4. task involving sysadmin/devops, I'll need your help to review. |
All of the above usecases are what we do inside Matrix AI already @tegefaulkes @DrFacepalm, so I'll be asking you separately to review different parts of this. |
Relevant issues:
|
This has all been migrated to https://github.com/MatrixAI/Polykey/wiki. Only reference articles and some special how tos as well as developer documentation goes to the subprojects now. |
I've added new links to the roadmap that will be relevant for all of us to read @tegefaulkes @joshuakarp @emmacasolin @scottmmorris @DrFacepalm especially as we develop the product roadmap and vision as well as the marketing materials (website, blog, presentations and workshops) during our release. We can want to make sure that our features have a tight focus on particular usecases and we need to prioritize our features so that it's a plan and not a wish list. |
Upgrading this to an epic as there is likely to be multiple subissues to write for Polykey. |
Alot of devops usecases can be written by composing the PK cli with other CLI tools. See details on push-integration here: MatrixAI/Polykey#174. |
Already specced as part of Polykey Documentation for 1.0.0. Closing this. |
Tasks
The text was updated successfully, but these errors were encountered: