Add option to provide separate config file [$25]

[wuuti]

Summary

Currently the .config-file is always used. It would be great to have an option

 --config <file>

where another config file can be provided.

This is useful e.g. for local dev installations where you have multiple "deployment" tasks in your wrapper scripts.

---

There is a $25 open bounty on this issue. Add to the bounty at Bountysource.

[ashu-22]

What Kind of steps Should I follow up on this request?

[hugopeek]

@ashu-22 You mean to claim the bounty? You'll need to create a pull request with the addition that @wuuti described above. Once that gets accepted and merged into the Gitify repository, the bounty is yours :)

Basically, you need to add the ability to run the following commands:

gitify build --config <file>
gitify extract --config <file>

Where <file> is a valid Gitify configuration file, other than the main .gitify.

[ghost]

Has this been resolved yet?

[Bruno17]

I've solved multiple configs by creating a folderstruture like that: modxroot/ -gitify/ --configA/ --configB/

and have a config.core.php within the config - directories with

<?php

include (dirname(dirname(dirname(__FILE__))) . '/' . 'config.core.php' );

running Gitify inside the config - folders

[hugopeek]

@Bruno17 Nice and elegant alternative! Works for me :+1:

[Bruno17]

@Mark-H maybe worth to put it to the docs?

[wuuti]

So that has been merged #417