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

Setup CLI #240

Open
JedPattersonn opened this issue Nov 14, 2024 · 1 comment · May be fixed by #344
Open

Setup CLI #240

JedPattersonn opened this issue Nov 14, 2024 · 1 comment · May be fixed by #344
Labels
enhancement New feature or request

Comments

@JedPattersonn
Copy link

Have you considered adding a CLI setup process, similar to how the T3 Stack does it? I'm a big fan of this project but find a lot of the features aren't relevant to me, especially as some require third-party services.

Would be great to have a custom setup experience, so I can say what I do/don't want, and then have options for each, such as Drizzle vs Prisma.

Would speed up the process a lot when first developing, as I don't need to go through the code and remove services I don't want to use.

@JedPattersonn JedPattersonn added the enhancement New feature or request label Nov 14, 2024
@haydenbleasel
Copy link
Owner

Hey @JedPattersonn, yep been thinking about that recently. I think as we build out more migration guides (e.g. switch your database to X or switch your auth provider to Y) we'll end up seeing patterns that will help us create more isolated packages. Then, as you noted, we can make those packages and even the specific providers customizable in the init command.

@haydenbleasel haydenbleasel linked a pull request Dec 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants