Go Google Sites Proxy

Project homepage: https://ggsp.fever.ch

Intro

A simple proxy for the New Google Sites.

Fall 2016, Google introduced New Google Sites, it's a very nice product, it allows the creation of nice and responsive websites that suits well either for mobile and desktop use.

Sadly, Google [at least at the time this text is being written, [August 24th, 2017] doesn't support the usage of a custom domain name yet [link].

Features

• Works with any domain!
• Support for custom favicon

Try it!

This software is already used in production. The website of this project also using it!

Config file format

port: 9080
sites:
  - ref: go-gsites-proxy                # the name of the website on Google Sites
    host: ggsp.fever.ch                 # the vhost linked with the current site
    language: en-US, en;q=0.9           # a language hint, to get a properly localized page
    description: Go Google Sites Proxy  # a short description of this site

To-Do

• add cache for the retrieved content

How to install

Build from sources

Fetch sources and build it:

go get -v -u github.com/fever-ch/go-google-sites-proxy

Once the get completes, you should find your new go-google-sites-proxy (or go-google-sites-proxy.exe) executable sitting inside $GOPATH/bin/.

Execute it

Create your own configuration file (formatted in yaml). This project contains an example named config-example.yaml(link).

nohup $GOPATH/bin/go-google-sites-proxy my-custom-config.yaml &

Use it with Docker :

Let's assume that the configuration file (config.yaml) is in my-config-folder

docker pull feverch/go-google-sites-proxy
docker run -d --name containerName -v /full-path/to/my-config-folder:/etc/ggsp/ -p 80:9080 feverch/go-google-sites-proxy

Build your own image with Docker

docker build .

Historically this project container's image was built with Rocker. Sadly Docker project has discontinued, but on the other hand, Docker implemented many of the exiting features that were brought by Rocker.

HTTPS, HTTP/2.0 support

Go Google Sites Proxy doesn't support yet, and might never, HTTPS and HTTP/2.0 protocols. Since these protocols are nowadays a must, but on the other hand, they require fine tuning, a clever approach would be to use NGINX (docker image) or to use a well-known service such that CloudFlare.

2017-2018 fever.ch - Raphaël P. Barazzutti