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

Allow minion backend to be configured from the conf file #16

Closed
mbroadhead opened this issue Apr 5, 2017 · 1 comment
Closed

Allow minion backend to be configured from the conf file #16

mbroadhead opened this issue Apr 5, 2017 · 1 comment

Comments

@mbroadhead
Copy link

mbroadhead commented Apr 5, 2017

Currently we are forced to use the Minion::Backend::File backend, which is depreciated (see #15). It would be nice if we could provide our own minion backend from the configuration file.

Instead of:

{
  minion_db_file => "./minion.data",
}

We could do:

{
  minion => { SQLite => 'sqlite:test.db' },
}

OR:

{
  minion => { Pg => 'postgresql://postgres@/test' },
}

This would allow users to use any Minion backend that they want, without having to modify the rex-jobcontrol source code.

@ehuelsmann
Copy link
Contributor

This has been implemented yesterday on the master branch. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants