google-sites-backup

Export a Google Site and save it locally on your computer.

Features and limitations:

• The saved copy represents the last revision of your site. No revision history is downloaded.
• The primary intend of this script is to backup your data. It does not support import back to Google Sites.
• Items in a "list page" and "web attachment" links are formatted and saved as separate files.
• Files in a "file cabinet page" may be categorized in folders. This info is saved in the "meta" files.
• The default output format of the saved pages may differ from what you see online at Google Sites. All your data however should be properly mirrored locally, and you can represent it later in any format.

Installation

mkdir ~/backup
cd ~/backup
git clone https://github.com/google/gdata-python-client.git
git clone https://github.com/famzah/google-sites-backup.git

Interactive execution

The default behavior is to ask for every configuration setting on the console:

google-sites-backup/run.sh gdata-python-client/ google-sites-backup/

Non-interactive execution

If you intent to run the backup script multiple times, you should consider the following approach:

google-sites-backup/run.sh gdata-python-client/ google-sites-backup/ \
  --client_id='%YOUR-OAUTH2-ID%' \
  --client_secret='%YOUR-OAUTH2-SECRET%' \
  --domain='%EMPTY_OR_ENTER_GOOGLE_APPS_DOMAIN%' \
  --site='mywikiexample' \
  --session_file=/var/tmp/gsites-token \
  --backup_dir=gdata-backup/

Notes:

• The "gdata-backup/" target directory must not exist.
• The "session_file" caches the authentication token, so that you don't have to switch to a browser and authorize the client for every site you want to backup.
• For most users, the "domain" option should be an empty string ''.
• You need your own OAuth 2.0 credentials:
  • Create a new project in the Google Developers Console on your account.
  • Activate the "Google Sites Data" API in the Google Developers Console. Navigate to "APIs & auth", then "APIs". If the API isn't listed in the Developers Console, then skip this step.
  • In the Google Developers Console, navigate to "APIs & auth", then "Credentials". Click the button "Add credentials" and choose "OAuth 2.0 client ID". Choose "other" for "Application type".
  • You can now see and use your client ID and client secret.

Tutorial

Here is a user-contributed tutorial: http://alvaro.cat/en/blog/google-sites-backup.html

Alternative implementations

The Google Sites Liberation project is written in Java. As of its latest release, it works only in GUI mode since OAuth2 is not supported in the non-interactive console mode. Future versions may fix this, so check regularly if this solution suits you better.