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

ui: Add subcommand to initialize a new local pallet #232

Open
ethanjli opened this issue Jun 13, 2024 · 1 comment
Open

ui: Add subcommand to initialize a new local pallet #232

ethanjli opened this issue Jun 13, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@ethanjli
Copy link
Member

ethanjli commented Jun 13, 2024

Currently, the Forklift CLI provides no way to initialize a new local pallet; that must instead be done using the Git CLI with git init (or some other Git tool) and by manually creating files (e.g. for forklift-pallet.yml). It would be nice if we could provide a CLI (and maybe also a simple TUI using https://github.com/charmbracelet/huh) to make it easier to initialize a new local pallet, e.g. via the plt init subcommand. It would also be great if the TUI could provide an initialization wizard to add any external package repos and package deployments needed by the user.

It would also make sense to make this subcommand work for dev plt init.

This functionality will become much more useful after we complete #253.

@ethanjli ethanjli added the enhancement New feature or request label Jun 13, 2024
@ethanjli ethanjli self-assigned this Jun 14, 2024
@ethanjli ethanjli added this to the Preprint Nice-to-Haves milestone Jun 14, 2024
@ethanjli ethanjli changed the title Add subcommand to initialize a new local pallet ui: Add subcommand to initialize a new local pallet Jun 14, 2024
@ethanjli
Copy link
Member Author

Part of the initialization flow could be an option to set up the local pallet as an override over an existing pallet (for customization), by setting up a requirement for that existing pallet, and maybe also some sort of local update-checking mechanism (or auto-upgrade mechanism) for that requirement (though it may be simpler/safer to just shift the responsibility of such auto-upgrades onto a remote host for the pallet, as in #242 with GitHub CI; in that case, we'd want to implement #233 with starter configs for auto-upgrading dependencies).

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

No branches or pull requests

1 participant