Feature Request: Custom Tasks

[vovimayhem]

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 script restoredb 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?

[vovimayhem]

@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?:

• Use a json settings file? (plis.json)
• Use a yaml settings file? (.plis.yml)

[vovimayhem]

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:

• Adding names to the /etc/hosts file to enable different domains/subdomains to resolve to localhost

[mayra-cabrera]

@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)