LuachSync

Hebrew Calendar for Google Calendar

The app is deployed at https://luachsync.elyasaf.net/

What This App Does

LuachSync is designed for recurring Hebrew-date events (for example, birthdays, yahrzeits, anniversaries, and memorial dates) and turns them into Gregorian calendar events that can be used in standard calendar systems like Google Calendar.

The app workflow is:

1. You enter an event using a Hebrew date (for example: 1 Nisan 5740).
2. The app calculates the corresponding Gregorian date for each yearly recurrence.
3. It repeats this calculation for a long planning range (up to 100 years).
4. It generates the full list of Gregorian events (first occurrence, second, third, and so on).
5. You can then either:
   • Export the events to an ICS file, or
   • Use automatic Google sync to create a dedicated calendar and upload all generated events.

Example:

• If you enter a Hebrew birthday such as 1 Nisan 5740, LuachSync computes when that birthday falls each year in the Gregorian calendar and creates the recurring series for up to 100 years.
• With Google sync, LuachSync creates a new calendar in your Google account and inserts those calculated Gregorian birthday events into that calendar.

Credits

Hebrew calendar calculations are powered by Hebcal: https://github.com/hebcal

Public Privacy Policy

See the privacy policy at: https://luachsync.elyasaf.net/privacy

Run Locally

Prerequisites: Node.js

1. Install dependencies: npm install

2. Create .env.local and set your keys:

   VITE_GOOGLE_CLIENT_ID=your_google_oauth_client_id

3. VITE_GOOGLE_CLIENT_ID is required for automatic Google Calendar sync (create new calendar + upload events).

4. Do not put OAuth Client Secret or service-account private keys in this project.

5. Run the app: npm run dev

1. Google Cloud Console

1. Create or select a Google Cloud project.
2. Enable Google Calendar API.
3. Create an OAuth 2.0 Client ID of type Web application.

2. OAuth Allowed Origins

Add these under Authorized JavaScript origins:

1. Local dev: http://localhost:3000
2. GitHub Pages origin: e.g., https://<username>.github.io

2.1 Existing Calendar Behavior

1. The app now asks for a custom target calendar name.
2. If a calendar with that exact name already exists in the signed-in account, you will get a confirmation warning.
3. If you approve, the existing calendar is deleted and recreated with the same name, and then events are imported via Google Calendar API.

3. Security Notes

1. Safe in frontend: OAuth Client ID.
2. Never expose in frontend: OAuth Client Secret, service-account JSON private key.
3. API key is not needed for this write flow.

Deploy to GitHub Pages

1. Build: npm run build
2. Deploy: npm run deploy
3. In repository settings, enable GitHub Pages from the gh-pages branch if not already enabled.