Checklist

• I have checked the issues list
  for simi

In the Readme, the documentation has "ignore_paths" in the YAML example, while it seems Realize is actually looking for "ignored_paths" as the key (per the JSON parsing annotations in https://github.com/oxequa/realize/blob/bcf8507c0bd7d33f54a8223c9e8fa1fd3e4a4555/realize/projects.go#L34).

Task has some tricky gotchas that are not well documented. I need to work on improving some areas and add some missing documentation.

• Add a variable priority section better explaining how them work.
  • Make it clear that setting a var through cli (not env) kinda overrides it. (Ref).
• More itens to be added

First of all, thanks for this awesome lib! :)

I'm trying to set the priority of RabbitMQ in a Middleware but I realized that the before_enqueue callback is called after the pika.BasicProperties creation.

Maybe these pro

Describe the bug
The Wiki describes install instructions for VVV, but these are manual instructions that would need to be redone on every new VM, and don't use the official way to install things

Expected behavior

Instructions on how to add a utility to config/config.yml that installs wordmove

https://varyingvagrantvagrants.org/docs/en-US/utilities/

Literally just cre

In .air.conf, if you set the tmp to ".", your entire current working directory will be wiped. This can be very bad especially if you haven't committed to git in a while. Can we have a warning if it is set to "." or atleast some documentation around that please?

My .air.conf that caused this:

# Working directory
# . or absolute path, please note that the directories following must be und

This is not currently being tested, and as it is a template method, we don't even check it builds correctly.

doit already support Task parameters, but they are not convenient to be used with task-groups.

Example of proposed feature:

from doit import task_param

@task_param({'name':'param1', 'short':'p', 'default':'default value'})
def task_py_params(param1):
    for name in ['foo', 'bar']:
        yield {
            'name': name,
            'actions':['echo {}'.format(param1)],
   

Adding documentation example of a working CI build using cirrus-ci.org (.cirrus.yml)

In the README the assets? task definition is a bit wrong.

    p.Task("assets?", nil,  func(c *do.Context) {
        // The "?" tells Godo to run this task ONLY ONCE regardless of
        // how many tasks depend on it. In this case watchify watches
        // on its own.
	    c.Run("watchify public/js/index.js d -o dist/js/app.bundle.js")
    }).Src("public/**/*.{css,js,html}")

The lib needs to be cleaned up and documented so others can use it more easily.

Currently, the (built-in) tasks documentation is a bit... lacking.
We only have a link to the src/builtin-tasks folder and that's it. Any user or developer interested would have to look deep into the sources to understand what is going on.

A suggestion to

In the documentation: https://dnephin.github.io/dobi/variables.html it says that variables can have default values. When I am building an image I would like dobi to resolve those defaults to their actual value. For example if I run b=1 dobi image/test I would like RUN echo ${evaluate} to print 1 instead of env.b, which is what happens now.

Do

The description in the readme is a bit confusing here

[...] for same project (example running scripts from package.json for multiple projects)

Is your feature request related to a problem? Please describe.
When running a help command on a values arg or option, no information about possible values is shown. The user has first to fail the command to see the values. I'd like to see them right when asking tusk for help, not when trying to execute and fail.

Also it'll be nice if I could define a usage info for values.

This also co