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

Override default tasks.py module name in invoke.yaml #455

Closed
dmulter opened this Issue Jul 6, 2017 · 6 comments

Comments

Projects
None yet
3 participants
@dmulter

dmulter commented Jul 6, 2017

I just migrated my Fabric setup over to Invoke, thanks a lot for the great work.

I've run into one issue that hopefully already has a solution. I'm using Celery across a number of apps and already have a tasks module. I've put my Invoke tasks in a invfile.py module and use the -c invfile option when I run invoke. Unfortunately that is not practical every time I run invoke.

I haven't found it, but is there a way I can specify the default module for invoke tasks in an invoke.yaml file in my app directory? Seems the most natural way to me.

@ploxiln

This comment has been minimized.

ploxiln commented Jul 6, 2017

If invoke.yaml is a standard named file for invoke to look for ... this just "kicks the can down the road" doesn't it? Can you just treat tasks.py as your invoke.yaml, the standard-named file that references custom files/paths?

@dmulter

This comment has been minimized.

dmulter commented Jul 6, 2017

I don't think so about the can... invoke.yaml is very clearly in the invoke namespace, so it makes sense to me that I would configure something like the default module (tasks, or something else). Again, the tasks module is already used for my Celery tasks across many apps, so I can't call it tasks.py

@ploxiln

This comment has been minimized.

ploxiln commented Jul 6, 2017

Ah. I see that celery also recommends using "tasks.py" and that invoke.yaml is already a standard filename invoke looks for. Makes sense

@bitprophet

This comment has been minimized.

Member

bitprophet commented Jul 7, 2017

Believe this duplicates #310, re: ability to tweak those low-level settings. Gonna merge this with that and put some updated thoughts in there, one sec.

@bitprophet bitprophet closed this Jul 7, 2017

@dmulter

This comment has been minimized.

dmulter commented Jul 7, 2017

thanks!

@bitprophet

This comment has been minimized.

Member

bitprophet commented Jul 7, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment