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

Enabling Integrations from command line arguments #54

Open
joncodo opened this issue Feb 27, 2023 · 2 comments
Open

Enabling Integrations from command line arguments #54

joncodo opened this issue Feb 27, 2023 · 2 comments

Comments

@joncodo
Copy link
Contributor

joncodo commented Feb 27, 2023

In my opinion, we should enable all apps possible on new application install. This means less work for our users and there is no downside to having all integrations possible.

This also means that we need a way to configure all integrations from the UI.

@seanspeaks
Copy link
Contributor

That sounds like a template to me.

And a built in scaffolding command to install a new api module.

The majority of the time so far, folks are adopting Frigg to power a specific integration, and will already have some integrations built out in a different way, so they're going to end up "uninstalling" all of the api modules they don't use.

FWIW, the frontend is dynamic, just needs "IntegrationConfigOptions" to have an entry per app.

@joncodo
Copy link
Contributor Author

joncodo commented Feb 27, 2023

This sounds like a great plan.

@joncodo joncodo changed the title The out of the box experience Enabling Integrations from command line arguments Feb 27, 2023
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

2 participants