Soylent-www - Revision history

Paulej72: /* Basic Information */

2014-08-21T19:03:57Z

Basic Information

← Older revision		Revision as of 19:03, 21 August 2014
Line 19:		Line 19:
	Only httpd does not* have an init script, needs to be fired manually via apachectl.		Only httpd does not* have an init script, needs to be fired manually via apachectl.

	There are several scripts for deployment and maintenance of Slash. They are located in /srv/soylentnews.org/bin/.		There are several scripts for deployment and maintenance of Slash. They are located in /srv/soylentnews.org/bin/. They are designed to be run as the slash user.

	{\| class="wikitable" width="100%"		{\| class="wikitable" width="100%"

Paulej72: /* Slash Config */

2014-08-19T03:32:46Z

Slash Config

← Older revision		Revision as of 03:32, 19 August 2014
Line 57:		Line 57:

	== Slash Config ==		== Slash Config ==
	~~No Idea~~, ~~I didn't set this up~~.		Most of Slash is configured via vars set in the Admin interface (Backslash) within the main site. There are so many settings it is crazy to list any here. One caveat is that many of the vars will not take immediate unless the Slash is reloaded using the reload-all-webfrontens script. The caches will eventually time out and the var, or other change will be seen by all users. If the change is critical, do a reload, if not just let the caches clear naturally.

	== Memcache Config ==		== Memcache Config ==

Paulej72: /* Varnish Config */

2014-08-19T03:17:29Z

Varnish Config

← Older revision		Revision as of 03:17, 19 August 2014
Line 48:		Line 48:

	== Varnish Config ==		== Varnish Config ==
	Varnish is a caching reverse proxy that listens on port 80 and proxies traffic to the local apache running on port 2600. It does the magic that transforms the data from the NodeBalancer to get data that Slash needs, specifically transforming the X-Forward-For and X-SSL-On headers so Slash ~~know~~ what IP address a user is coming from and if they are using SSL.		Varnish is a caching reverse proxy that listens on port 80 and proxies traffic to the local apache running on port 2600. It does the magic that transforms the data from the NodeBalancer to get data that Slash needs, specifically transforming the X-Forward-For and X-SSL-On headers so Slash knows what IP address a user is coming from and if they are using SSL.

	~~Varnish~~ is set to use memory for its cache and ~~is currently set~~ to use 512 MBi.		The varnish config file is /etc/vanish/soylentnews.vcl and is set to use memory for its cache and to use 512 MBi. It is also set to cache only static objects: css, js, gif, jpeg, etc, and specifically passes the login, comments, subscribe, and users pages uncached.

	It is ~~current~~ set to cache only ~~status~~ objects: css, js, gif, jpeg, etc, and specifically passes the login, comments, subscribe, and users pages uncached.

	== Apache Config ==		== Apache Config ==

Paulej72: /* Apache Config */

2014-08-19T03:14:48Z

Apache Config

← Older revision		Revision as of 03:14, 19 August 2014
Line 56:		Line 56:
	== Apache Config ==		== Apache Config ==

	Listening on port 2600, there is a setting in one of the slash includes to get perl to recognize the XFF header stuff. Most of this is manage through Slash, either during the initial install or by setting one of the many Slash vars.		Listening on port 2600, there is a setting in one of the slash includes to get perl to recognize the XFF header stuff. Most of this is manage through Slash, either during the initial install or by setting one of the many Slash vars. Typically this needs no direct editing of the config file.

	== Slash Config ==		== Slash Config ==

Paulej72: /* Memcache Config */

2014-08-19T03:14:00Z

Memcache Config

← Older revision		Revision as of 03:14, 19 August 2014
Line 62:		Line 62:

	== Memcache Config ==		== Memcache Config ==
	This caches mysql queries so fewer queries have to go back to the db.		This caches mysql queries so fewer queries have to go back to the db. Config file is in /etc/memcached.conf and is set to use 512 Mbi of memory and to listen on port 11211 on both the loopback address and the ipv4 address of the server.
	~~I didn't~~ set ~~this up, someone else need~~ to ~~document~~ the ~~config~~.

	[[Category:System administration]]		[[Category:System administration]]

Paulej72: /* Apache Config */

2014-08-19T03:09:18Z

Apache Config

← Older revision		Revision as of 03:09, 19 August 2014
Line 56:		Line 56:
	== Apache Config ==		== Apache Config ==

	Listening on ~~Port~~ 2600, there is a setting in one of the slash includes to get perl to recognize the XFF header stuff		Listening on port 2600, there is a setting in one of the slash includes to get perl to recognize the XFF header stuff. Most of this is manage through Slash, either during the initial install or by setting one of the many Slash vars.

	== Slash Config ==		== Slash Config ==

Paulej72: /* Nginx Config */

2014-08-19T03:07:26Z

Nginx Config

← Older revision		Revision as of 03:07, 19 August 2014
Line 53:		Line 53:

	It is current set to cache only status objects: css, js, gif, jpeg, etc, and specifically passes the login, comments, subscribe, and users pages uncached.		It is current set to cache only status objects: css, js, gif, jpeg, etc, and specifically passes the login, comments, subscribe, and users pages uncached.

	~~== Nginx Config ==~~
	~~No idea, I didn't set this up.~~

	~~If it's passing to Varnish, it probably won't work because slash is brain-dead about upstream reverse proxies and doesn't really parse the X-Forwarded-For header properly.~~

	~~If it's passing directly to the local apache, it might work a bit better.~~

	== Apache Config ==		== Apache Config ==

Paulej72: /* Varnish Config */

2014-08-19T03:07:08Z

Varnish Config

← Older revision		Revision as of 03:07, 19 August 2014
Line 50:		Line 50:
	Varnish is a caching reverse proxy that listens on port 80 and proxies traffic to the local apache running on port 2600. It does the magic that transforms the data from the NodeBalancer to get data that Slash needs, specifically transforming the X-Forward-For and X-SSL-On headers so Slash know what IP address a user is coming from and if they are using SSL.		Varnish is a caching reverse proxy that listens on port 80 and proxies traffic to the local apache running on port 2600. It does the magic that transforms the data from the NodeBalancer to get data that Slash needs, specifically transforming the X-Forward-For and X-SSL-On headers so Slash know what IP address a user is coming from and if they are using SSL.

	Varnish is set to use memory for its cache and is currently set to use ~~512MBi~~.		Varnish is set to use memory for its cache and is currently set to use 512 MBi.

	It is current set to cache only status objects: css, js, gif, jpeg, etc, and specifically passes the login, comments, subscribe, and users pages uncached.		It is current set to cache only status objects: css, js, gif, jpeg, etc, and specifically passes the login, comments, subscribe, and users pages uncached.

Paulej72: /* Varnish Config */

2014-08-19T03:02:30Z

Varnish Config

← Older revision		Revision as of 03:02, 19 August 2014
Line 48:		Line 48:

	== Varnish Config ==		== Varnish Config ==
	Varnish is a caching reverse proxy that listens on port 80 and proxies traffic to the local apache running on port 2600. It does the magic that transforms the data from the NodeBalancer to get data that Slash needs, specifically transforming the X-Forward-For and X-SSL-On headers so Slash know what IP address a user is coming from and if they are using SSL.		Varnish is a caching reverse proxy that listens on port 80 and proxies traffic to the local apache running on port 2600. It does the magic that transforms the data from the NodeBalancer to get data that Slash needs, specifically transforming the X-Forward-For and X-SSL-On headers so Slash know what IP address a user is coming from and if they are using SSL.

	It's current set to cache only status objects: css, js, gif, jpeg, etc, and specifically passes the login, comments, subscribe, and users pages uncached.		Varnish is set to use memory for its cache and is currently set to use 512MBi.

			It is current set to cache only status objects: css, js, gif, jpeg, etc, and specifically passes the login, comments, subscribe, and users pages uncached.

	== Nginx Config ==		== Nginx Config ==

Paulej72: /* Varnish Config */

2014-08-19T02:59:47Z

Varnish Config

← Older revision		Revision as of 02:59, 19 August 2014
Line 48:		Line 48:

	== Varnish Config ==		== Varnish Config ==
	Varnish is a caching reverse proxy that listens on port 80 and proxies traffic to the local apache running on port 2600.		Varnish is a caching reverse proxy that listens on port 80 and proxies traffic to the local apache running on port 2600. It does the magic that transforms the data from the NodeBalancer to get data that Slash needs, specifically transforming the X-Forward-For and X-SSL-On headers so Slash know what IP address a user is coming from and if they are using SSL.

	It's current set to cache only status objects: css, js, gif, jpeg, etc.		It's current set to cache only status objects: css, js, gif, jpeg, etc, and specifically passes the login, comments, subscribe, and users pages uncached.

	== Nginx Config ==		== Nginx Config ==