-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
A CLI #56
Comments
Considering that (aside from configuring .env variables) it is only two steps. Cloning, and installing dependencies. I don't really think it is necessary and I believe better time can be spend working on OrbitKit itself. I left out configuring .env variables because often times you might start your project (or at least clone it) before you have all of your .env variables configured. That being said it would definitely be helpful. Probably just not worth time time. |
It would be nice to have in the far future, but i think the main objective now is to get the starterkit complete. |
Seems reasonable. |
Is your feature request related to a problem? Please describe.
As per docs, Orbitkit requires manual setup and installation which seems an excellent scenario for a CLI!
Describe the solution you'd like
A CLI, inspired by create-t3-app, that performs the same exact steps ( at least for know ) mentioned in the installation section.
Describe alternatives you've considered
N/A
Additional context
This feature is related to #21, although achieving the desired outcome mentioned in the issue will require notable changes in how the repo is structured ( or not! ).
As for now the CLI can just perform the manual steps of installation, and in the future additional features and decisions could be made.
If this is acceptable I can gladly make a PR for it!
The text was updated successfully, but these errors were encountered: