-
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
Feature Request: Custom Tasks #12
Comments
@mayra-cabrera Asking you as our Go-Guru :) Given we're already parsing YAML in this project for the groups feature... Which is better/simpler to use?:
|
Given that we're starting to contemplate having a settings file of some sort, we should explore if there are more things for Plis to do, for example:
|
@vovimayhem woohaa I didn't see this before! Definitely I'm more inclined to use YAML for configuration files (it's also used as a standard for go configuration files) |
I like the idea of how npm allows tasks to be defined in the
package.json
file.Currently at IcaliaLabs, when we use plis inside a project, the most executed tasks are these:
plis run postgres restoredb some_database_name path/to/some/database.dump
(Uses a scriptrestoredb
to restore a database from a dump file)plis run web rails db:migrate searchkick:reindex:all another:rake:task
(Runs a bunch of rake tasks in a rails project)plis build service_a service_b service_c
(Re-builds the dockerfiles referenced by the compose project)Maybe we should be able to define these tasks in a file similar to how npm's
package.json
does.IMPORTANT Having a config file must not be mandatory.
Would this file be a json? a YML?
The text was updated successfully, but these errors were encountered: