Hi,

What you should do is add a block like this

$__instances['live'] = array(
    'prefix' => 'yourjobberbasedomain.com',
    'db_host' => 'localhost',
    'db_port' => 3306,
    'db_user' => 'root',
    'db_password' => '',
    'db_name' => 'jobberbase',
    'db_prefix' => '',
    'app_url' => 'http://www.yourjobberbasedomain.com/',
    'ini_error_reporting' => E_ALL,
    'ini_display_errors' => 'Off',
    'location' => 'online',
    'environment' => 'prod',
    'rewrite_mode' => 'apache_mod_rewrite'
);

in _config/config.envs.php for every domain you want to use JB on. You can add the blocks after the existing one. You have to change 'live' with 'live1', 'live2' or something else unique and then change the 'prefix'  and 'app_url' accordingly to every domain you want the site on.

Let us know if it works.

I am having a similar issue, but with sub-domains. The version I am working with is an older one, I adopted this job, and have no idea how they have it set up. This is set up on a Wordpress Mu installation with 6 sub-domains.

I have all the various $_instances blocks set up in the config.envs.php file and most of them work correctly. But when I try to add a new instance for a new sub-domain, it doesn't register and it bounces to an existing domain's job board. I have looked at all the .htaccess files and none are redirecting any of the sub-domains.

Here's the real kicker, there is a typo in the $_instances blocks already in place in some of the 'app_url' definitions (e.g. 'app_url' => 'http://colorado.mydomain.com/jobbboard/') - notice the extra 'b' in the directory folder name? It should be /jobboard/ but doesn't appear to be causing any problems.

Here is an example one of the working blocks:

$__instances['live4'] = array(
    'prefix' => 'colorado.',
    'db_host' => 'localhost',
    'db_port' => 3306,
    'db_user' => 'jobs1',
    'db_password' => 'Pass12345',
    'db_name' => 'jobs_colo',
    'db_prefix' => '',
    'app_url' => 'http://colorado.mydomain.com/jobbboard/',
    'ini_error_reporting' => E_ALL,
    'ini_display_errors' => 'On',
    'location' => 'online',
    'environment' => 'prod',
    'rewrite_mode' => 'apache_mod_rewrite'
);

Now, I am aware that the 'prefix' definition should the the root domain, correct? (e.g. mydomain.com) However, for most all of the working blocks, this is how the 'prefix' is defined. There is one block that has the full domain, including the sub-domain, defined in the prefix and it is working as well. (e.g. nc.mydomain.com)

So, needless to say, I am befuddled and confused. Any suggestions?