Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add support for --private to server.js (for my private builds only)

Browse source
This commit is contained in:
Jeff Parsons 2016-04-14 22:56:51 -07:00
commit 3c8e7fb78f
2 changed files with 7 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
modules/htmlout/lib/htmlout.js
View file

@ -89,7 +89,10 @@ var fServerDebug = false;
var logFile = null; var logFile = null;
/* /*
* fPrivate determines the insertion of private.js * fPrivate will be set to true to by setOptions() if the server was started with '--private', giving the Node
* server an option comparable to Jekyll's site.pcjs.private setting, and triggering the load of "private.js" as
* appropriate. Currently, the only (checked-in) use of the private setting is to set the client's PRIVATE global
* and trigger the loading of alternate (ie, private) XML files in embed.js.
*/ */
var fPrivate = false; var fPrivate = false;

3
modules/shared/lib/private.js
View file

@ -38,5 +38,8 @@
* PRIVATE enables certain private features that we don't want enabled on the public web server, so by default, * PRIVATE enables certain private features that we don't want enabled on the public web server, so by default,
* PRIVATE is false. For Jekyll configurations, if site.pcjs.private is set, this file gets included, overriding * PRIVATE is false. For Jekyll configurations, if site.pcjs.private is set, this file gets included, overriding
* the default. * the default.
*
* Currently, the only (checked-in) use of the private setting is to set the client's PRIVATE global and trigger
* the loading of alternate (ie, private) XML files in embed.js.
*/ */
PRIVATE = true; PRIVATE = true;