Metadata-Version: 2.4
Name: gcalvault
Version: 2.0.3
Summary: Command-line utility which exports all of a user's Google Calendars to iCal/ICS format for backup (or portability)
Home-page: http://github.com/rtomac/gcalvault
Author: Ryan Tomac
Author-email: ryan@tomacfamily.com
License: MIT
Keywords: Google Calendar,gcal,backup,export,iCal,ICS,CalDav
Classifier: Development Status :: 7 - Inactive
Classifier: Environment :: Console
Classifier: Intended Audience :: End Users/Desktop
Classifier: Natural Language :: English
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.9
Classifier: Topic :: System :: Archiving :: Backup
Requires-Python: >=3.9
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: google-api-python-client==2.181.*
Requires-Dist: google-auth-httplib2==0.2.*
Requires-Dist: google-auth-oauthlib==1.2.*
Requires-Dist: requests==2.32.*
Requires-Dist: GitPython==3.1.*
Requires-Dist: python-dotenv==1.1.*
Provides-Extra: dev
Requires-Dist: pycodestyle; extra == "dev"
Requires-Dist: setuptools; extra == "dev"
Provides-Extra: test
Requires-Dist: pytest==8.*; extra == "test"
Provides-Extra: release
Requires-Dist: twine; extra == "release"
Dynamic: author
Dynamic: author-email
Dynamic: classifier
Dynamic: description
Dynamic: description-content-type
Dynamic: home-page
Dynamic: keywords
Dynamic: license
Dynamic: license-file
Dynamic: provides-extra
Dynamic: requires-dist
Dynamic: requires-python
Dynamic: summary

> **⚠️ This project is no longer maintained.** For automated backup of Google calendars, I would recommend [vdirsyncer](https://vdirsyncer.pimutils.org). For one-time backups, [Google Takeout](https://takeout.google.com) works fine.

# Overview

Gcalvault is a command-line utility which exports all of a user's Google Calendars to iCal/ICS format for backup (or portability).

Features:
- Automatically discovers all calendars visible the user
- Downloads them in iCal/ICS format and saves them to disk for archival
- Optionally manages version history for each calendar in an on-disk "vault" (a git repo under the covers)
- Can be run via Docker image (multi-arch) or installed directly as a Python package with command-line interface

# How it works

- Uses Google's [Identity Provider](https://developers.google.com/identity/protocols/oauth2) to authenticate (via OAuth2/OIDC)
- Uses Google's [Calendar API](https://developers.google.com/calendar/api/v3/reference) to discover a user's calendars
- Uses Google's [CalDAV endpoints](https://developers.google.com/calendar/caldav/v2/guide) to download iCal/ICS calendars
- Uses [GitPython](https://gitpython.readthedocs.io) to manage local git repo for version history under the covers

# Usage

Some example commands...

Sync all calendars for `foo.bar@gmail.com` user:
```
gcalvault sync foo.bar@gmail.com
```

Sync one specific calendar:
```
gcalvault sync foo.bar@gmail.com family123@group.calendar.google.com
```

Sync only "writable" calendars:
```
gcalvault sync foo.bar@gmail.com --ignore-role reader
```

Simply export calendars, do not save version history:
```
gcalvault sync foo.bar@gmail.com --export-only
```

See the [CLI help](https://github.com/rtomac/gcalvault/blob/main/src/gcalvault/USAGE.txt) for full usage and other notes.

# Requirements

- Python 3.9+

# Installation

## Via PyPi

```
pip install gcalvault
gcalvault sync foo.bar@gmail.com
```

## Via Docker

```
docker run -it --rm \
    -v ${HOME}/.gcalvault:/root/.gcalvault \
    -v ${PWD}/gcalvault:/root/gcalvault \
    rtomac/gcalvault sync foo.bar@gmail.com
```

# OAuth2 authentication

The CLI initiates an OAuth2 authentication the first time it is run (interactive), and then uses refresh tokens for subsequent runs (headless).

When you use Gcalvault in its default configuration, you are initiating the OAuth2 flow with Google using Gcalvault's client ID. There is nothing inherently insecure about this, since the application is running locally and therefore only *you* will have access to the data it reads from Google.

That said, it is recommended to create your own client ID through the [Google API Console](https://console.developers.google.com/), since the shared client ID may be used by others and subject to limits which may cause unpredictable failures.

[rclone](https://rclone.org) has a good write-up on [making your own client ID](https://rclone.org/drive/#making-your-own-client-id).

You can provide your client ID and secret to gcalvault as follows:
```
gcalvault sync foo.bar@gmail.com --client-id my_client_id --client-secret my_client_secret
```

If you are providing your own Google OAuth2 client, you will need to ensure the following APIs and OAuth2 scopes are enabled for the project/client in GCP.

Google APIs:
- Google Calendar API: `calendar-json.googleapis.com`
- CalDAV API: `caldav.googleapis.com`

OAuth2 scopes:
- `openid`
- `https://www.googleapis.com/auth/userinfo.email`
- `https://www.googleapis.com/auth/calendar.readonly`

# Development

Source repository:<br>
http://github.com/rtomac/gcalvault

## Install dependencies and run locally
```
pip install virtualenv
make devenv
. ./.devenv/bin/activate
gcalvault --help
```

## Run tests
```
pytest
```

## Build distribution
```
make dist
```

## Build Docker image
```
make docker-build
```

## Run via Docker image
```
make docker-run user=foo.bar@gmail.com
```

## Release to PyPi and Docker Hub
```
make release
```

See targets and variables in [Makefile](https://github.com/rtomac/gcalvault/blob/main/Makefile) for more options.

# License

MIT License
