Working on local server and upload to website

Mowgli76

Hi

I usually work on a local server setup

When I'm done, I upload changed files to my online website

The problem with that, when uploading to the website, is that the Vanilla config files etc. gets overwritten too and now no longer matches the online forum/server/db setup

How do you go about this?

And if I change a lot of dashboard settings.. which files or database tables/rows/fields should I re-upload?

Bleistivt

Config settings are almost exclusively saved in conf/config.php

I would not recommend cherry picking tables to update, e.g. when you edit permissions.

Categories, users and permissions are saved in the database, everything else you can edit through the dashboard is saved in config.php

Mowgli76

Ok But how to handle 2 separate config files.. Do you know?

Bleistivt

I don't really understand your question.
Do you want to split the config file in multiple files?

Mowgli76

Local server has one config file:

$Configuration['Database']['User'] = 'qwertyqwerty';
$Configuration['Database']['Password'] = 'qwerty123';
$Configuration['Debug'] = TRUE;

Online website has a different config file (obviously, because the environment is not the same):

$Configuration['Database']['User'] = 'onlinemaster';
$Configuration['Database']['Password'] = 'helloHello999';
$Configuration['Debug'] = FALSE; (!)

What happens when you upload all your local files, including config files? > The online website would display debugging info (baad) and simply not work

Bleistivt

Put the database information and debug line into something like config.env.php

Create a php file bootstrap.early.php

<?php if (!defined('APPLICATION')) exit();

Gdn::Config()->Load(PATH_CONF.'/config.env.php');

put it in the conf directory, too

This will only work for values that you don't change through the dashboard (like debug or db info), the forum will always write to config.php

whu606

@Mowgli76‌

Why not just change your local user and p/w details to reflect your online one, and leave debug set to false until you need it?

Mowgli76

Bleistivt, Ok maybe I will try that, thanks

whu606, well that could be a good solution. If I can change it all. But then there is still the 2 different settings for debugging

Bleistivt

This actually takes precedence over the config.php, so I'd recommend leaving the config of your production site the way it is and add this only to your dev environment.

whu606

@Mowgli76‌

I'm not sure how often you make changes, but I can't see changing 'true' to 'false' in the debug line as being that onerous!

For the DB, you can create a new user in phpMyAdmin to match your online one, and copy your DB and give it the name of your live DB.

Personally, I use a local install to test ideas/edits, and a copy of my live install on my webserver for changes I want to see in my production site.

hgtonight

For websites that I test locally and deploy via git, I don't track the config file at all. Sure, I have to propagate configuration changes, but how often does that need to be done?