tulbox

Configuring Cloudflare SSL/TLS on Google App Engine

Implementing end-to-end HTTPS encryption with CloudFlare for Google App Engine applications.

Google App Engine - Custom Domains

Add Domains

Register the root domain with Google Cloud Platform at the following:

I am having trouble getting this to work. I'm trying to get the material ui leftNav to work with react router and redux with nav going through the store and router. This was close, but didn't get all the way to the menu item.

TypeError: Cannot read property 'isActive' of undefined

I was also referring to these examples: https://github.com/callemall/material-ui/blob/master/docs/src/app/components/app-left-nav.jsx

http://codetheory.in/react-integrating-routing-to-material-uis-left-nav-or-other-components/

Install npm and nodejs (on debian I had to link /usr/bin/nodejs to /usr/bin/node
At the root of your project create package.js file with the an empty json object:

$ echo "{}" > package.js

In the same directory, install all the project dependencies with the following command:

	(function (context, trackingId, options) {
	const history = context.history;
	const doc = document;
	const nav = navigator \|\| {};
	const storage = localStorage;
	const encode = encodeURIComponent;
	const pushState = history.pushState;
	const typeException = 'exception';
	const generateId = () => Math.random().toString(36);
	const getId = () => {

	import ReactSelect from 'react-select';
	import Portal from 'react-overlays/lib/Portal';

	import 'react-select/dist/react-select.css'; // I'm using css-modules, but you can use whatever you like
	import css from './Select.css';
	import defaultMenuRenderer from 'react-select/lib/utils/defaultMenuRenderer'; // this renders the actual menu - we can reuse the same component

	class _SelectMenu extends React.Component {
	props: { // flow types
	selectProps: {},

	React.createClass({
	displayName: 'Name',

	propTypes: {},
	mixins: [],

	getInitialState: function() {
	return {};
	},
	getDefaultProps: function() {

	using System.Collections.Generic;
	using System.Diagnostics;
	using System.Web.Http;
	using System.Web.Http.Controllers;
	using System.Web.Http.Filters;
	using Castle.Windsor;
	using Algorythmic.Web.API.Filters;

	namespace Algorythmic.Web.API.Windsor.Filters
	{

	Param(
	[Parameter(Mandatory=$true)] $path
	)

	$proxyHtm = @"
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
	<html xmlns="http://www.w3.org/1999/xhtml" >
	<head>
	<title>Repo proxy</title>
	</head>

	/*
	While generally using HttpContext, and all of the related properties such as
	Cookies and Session, in WebAPI is not the right way sometimes it needs to be
	done, especially when migrating existing code before doing a full rewrite but
	could happen in any legacy MVC project you want to bring WebAPI into.

	When using Autofac there is the AutofacWebTypesModule which allows you to resolve
	these dependencies, all of which come from resolving HttpContextBase.

	WebAPI doesn't provide HttpContext directly but if hosted in IIS rather than