<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>dashing &#8211; Diary of an Emacs tragic</title>
	<atom:link href="https://emacstragic.net/tag/dashing/feed/" rel="self" type="application/rss+xml" />
	<link>https://emacstragic.net</link>
	<description>Jason Lewis</description>
	<lastBuildDate>Tue, 04 Mar 2014 01:41:46 +0000</lastBuildDate>
	<language>en-AU</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>

<image>
	<url>https://emacstragic.net/wp-content/uploads/2018/12/cropped-jason-lewis-profile-picture-square-150x150.jpg</url>
	<title>dashing &#8211; Diary of an Emacs tragic</title>
	<link>https://emacstragic.net</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">38469313</site>	<item>
		<title>Proxy Dashing Dashboard behind Apache with SSL</title>
		<link>https://emacstragic.net/uncategorized/proxy-dashing-dashboard-behind-apache-ssl/</link>
					<comments>https://emacstragic.net/uncategorized/proxy-dashing-dashboard-behind-apache-ssl/#comments</comments>
		
		<dc:creator><![CDATA[Jason]]></dc:creator>
		<pubDate>Tue, 04 Mar 2014 01:41:46 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[dashing]]></category>
		<guid isPermaLink="false">http://emacstragic.net/?p=943</guid>

					<description><![CDATA[I needed to allow access to my Dashing dashboard over ssl from the Internet.  I decided to proxy it behind Apache and get Apache to do all the SSL heavy lifting, mainly because I couldn&#8217;t work out if and how you could enable SSL within Dashing itself. It turned out to be quite simple to [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>I needed to allow access to my <a title="Dashing dashboard framework" href="https://github.com/Shopify/dashing">Dashing</a> dashboard over ssl from the Internet.  I decided to proxy it behind Apache and get Apache to do all the SSL heavy lifting, mainly because I couldn&#8217;t work out if and how you could enable SSL within Dashing itself.<br />
It turned out to be quite simple to implement. I simply created a vhost configuration for my dashboard and enabled it in Apache.<br />
Create a file  called dashboard in /etc/apache2/sites-available/ with the following content:</p>
<pre>&lt;VirtualHost *:80&gt;
 ServerName dashboard.example.com
 Redirect permanent / https://dashboard.example.com/
&lt;/VirtualHost&gt;
NameVirtualHost *:443
&lt;VirtualHost _default_:443&gt;
 SSLEngine On
 SSLCertificateFile /etc/ssl/CAcert.cert.pem
 SSLCertificateKeyFile /etc/ssl/private/key.pem
 ServerAdmin webmaster@localhost
 ServerName dashboard.example.com
 ErrorLog "/var/log/apache2/dashboard-error_log"
 CustomLog "/var/log/apache2/dashboard-access_log" common
 &lt;Proxy *&gt;
   Order allow,deny
   Allow from all
 &lt;/Proxy&gt;
 ProxyPass / http://mylocalserver.example.com:3030/
 ProxyPassReverse / http://mylocalserver.example.com:3030/
&lt;/VirtualHost&gt;</pre>
<p>Ensure the proxy modules are enabled:</p>
<pre>$ sudo a2enmod proxy
Enabling module proxy.
To activate the new configuration, you need to run:
service apache2 restart
$ sudo a2enmod proxy_http
Enabling module proxy_http.
To activate the new configuration, you need to run:
service apache2 restart
$</pre>
<p><span style="line-height: 1.714285714; font-size: 1rem;">Enable the new dashboard site:</span></p>
<pre>$ sudo a2ensite dashboard</pre>
<p>Check your configuration is working before restarting apache:</p>
<pre>$ sudo apachectl configtest
Syntax OK
$ sudo service apache2 restart
[ ok ] Restarting web server: apache2 ... waiting .
$</pre>
<p>Don&#8217;t forget to delegate your dashboard.example.com hostname to resolve to your apache server&#8217;s IP address.<br />
Now visit http://dashboard.example.com/name_of_your_dashboard. Your browser should automatically get redirected to https://dashboard.example.com/name_of_your_dashboard and you should see your dashboard.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://emacstragic.net/uncategorized/proxy-dashing-dashboard-behind-apache-ssl/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">943</post-id>	</item>
	</channel>
</rss>
