Labai prasau lietuviskai paaiskinkite...
2016 sau. 21 23:38 "Jonathan Aquilina" rašė:
> I personally would use the .gitignore to not push the settings file to the
> repository and the just keep manual backups.
>
> Sent from my iPhone
>
> > On 20 Jan 2016, at 15:56, Ray Paseur wrote:
> >
> > Coll
I personally would use the .gitignore to not push the settings file to the
repository and the just keep manual backups.
Sent from my iPhone
> On 20 Jan 2016, at 15:56, Ray Paseur wrote:
>
> Colleagues: I'm looking for some "best practices" advice here.
>
> I have three Wikis, Dev, Test, and
"";
$GLOBALS["siteName"] = $wgSitename;
$wgMetaNamespace = "";
$wgLogo = "/skins/chameleon/ex.png";
$wgScriptPath = "";
$wgServer = "";
$wgDBserver = "";
$wgDBname = "";
$wgTmpDirectory = "$IP/images/temp";
$w
On Wed, Jan 20, 2016 at 7:56 AM, Ray Paseur wrote:
> Colleagues: I'm looking for some "best practices" advice here.
>
> I have three Wikis, Dev, Test, and Prod. Dev is the sandbox. Test is for
> user-acceptance. Prod is the public face - exactly what you would expect.
>
> For the most part, t
Hi Ray,
we have published our LocalSettings.php and simply excluded the
"secrets" which are in a separated folder (and excluded with .gitignore)
see Line 44 for example:
https://github.com/dennisroczek/TDFWIKI_settings/blob/master/TDFWIKI_LocalSettings.php#L44
You can include with such a constel
Colleagues: I'm looking for some "best practices" advice here.
I have three Wikis, Dev, Test, and Prod. Dev is the sandbox. Test is for
user-acceptance. Prod is the public face - exactly what you would expect.
For the most part, these Wikis share an identical code base on Git branch
"master
