-
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
Abstract Kernel and Plugin Setup into UI #18
Comments
Is this intended to be for the partner or plugin devs I'm a little confused because
Between the kernel GUI (it'll be more than a CLI I'd imagine if following probot's approach) and this config editor both devs and partners should be able to set things up through UIs (albeit two separate UIs but I think that makes sense) I might be wrong and it will be a CLI but I recall probot having an interactive UI that would deploy locally for you and it would ping certain things to confirm you had set things up properly and walk you through steps. |
I thought about it for contributors, I understand partners use our infra. My final idea was to have a one click setup and a UI for live logs, those could be useful in QA. It might not be worth the work tho. |
Dockerizing everything has been discussed and I'm sure 0x4007 made a monorepo of sorts which pulled in everything as an alternative but I don't think what you are suggesting has been discussed yet. Doesn't sound urgent but long term I think something like that would be cool. Hooked into your worker logs and displayed in a simple UI sounds nice because having multiple tabs of CF live-logs sucks lmao. I know you can |
Not sure if this fits here or in ubiquity-os-kernel. As soon as the CLI tooling to setup kernel is merged, we can take our first shot into abstracting the entire kernel and plugin setup into an UI, at least the worker ones. By authenticating with Cloudflare and GitHub we should be able to not only deploy the workers (kernel and plugins), but setup the repos for the org as well. Then, I believe it'd make sense for the plugin installer to become more than a yml editor, and to handle activating workers, updating repos...
The text was updated successfully, but these errors were encountered: