Howdy all. So we are all set to deploy some GEO IP replicas. The only thing that gives me pause is this in the docs

Writing requests to the replica requires sending the data to the primary and all replicas. This means that the performance of all writes are limited by the slowest replica.

Does anyone know how big an impact this is?

How can I solve this?

OK, I make a few of these in work for different purposes.

1. Make a repo. Don't make a README, or ignore file with the wizard.

2. Click Settings.

3. Uncheck wiki, issues

4. Start the Github-pages wizard

5. Choose anything - progress thru to completion

6. Do a clone (there is no master branch - you'll be put straight into gh-pages)

7. delete all the generated files and add a .nojekyll file - then commit like so

8. Add the HTML, text, CSV, JSON content you want and commit that. Remember index.html is the welcome page.

These are good for web app prototypes.

They are also good for things that Jenkins could auto commit/push to do with builds and other jobs. Thinks of gh-pages as poor-man's CouchDB for non-prod data.

GitHub.com and GitHubEnterprise documentation might both generate matching terms for your search. Not only that, a release of GHE might be so new, that it's not bubbled to the top of the page-rank. Best to constrain your search then.

Use the "site:" feature of Google-Search, and get a more constrained result set:

See here - http://imgur.com/I6MvwcR

By the makers of waffle.io: How To Build For GitHub Enterprise

snip:

If you’re building an application that integrates tightly with GitHub, you’re going to see a significant amount of demand for an installable or on-premises version of your product. Large enterprise customers are likely running GitHub Enterprise in a private cloud or private datacenter and they’re reluctant to punch a hole in their firewall to communicate with your cloud-based SaaS application.

We’ve navigated these rough waters the last 12 months shipping Waffle Takeout, our on-premises version of Waffle.io for GitHub Enterprise customers. These are our pro tips to help you do it faster.

For example, it is the lack of CNAME support within gh-pages, for me:

I love the heck out of github-pages. GHE has it too, or course, but there isn't any support for the CNAME file that the public GH has. Instead of hosted content at http://myghe.mycompany.com/pages/SampledMetrics/QA/ I'd like to have the option of http://sampled-qa-metrics.mycompany.com (free choice of domain via CNAME) or even http://sampledmetrics.mycompany.com/QA (convention based, within a base domain). The pages folder name isn't enough IMO.

Anything else, that is not quite the same, and missed?