Calendar of all calendars: aggregate many sources in one calendar and filter out
Find a file
2024-01-26 11:28:37 +01:00
data feat(calendars.json): Add new hackENS calendar 2024-01-16 18:35:35 +01:00
npins switch to npins and buildNpmPackage 2023-07-23 16:21:13 +02:00
public Rebrand from Club Réseau to DGNum 2023-09-28 12:48:18 +02:00
scripts first commit 2021-11-15 01:34:24 +01:00
src Rebrand from Club Réseau to DGNum 2023-09-28 12:48:18 +02:00
.drone.yml ci: build homepage on our Drone 2021-11-20 00:14:47 +01:00
.envrc Rajoute la banda et DDR (#51) 2022-09-12 13:30:29 +02:00
.gitignore switch to npins and buildNpmPackage 2023-07-23 16:21:13 +02:00
default.nix feat(npm): Update dependencies 2024-01-26 11:28:37 +01:00
package-lock.json feat(npm): Update dependencies 2024-01-26 11:28:37 +01:00
package.json Add bootstrap as dev dependency 2022-07-28 13:43:44 +02:00
prettier.config.js nix: nixify the setup, add prettier 2021-11-20 00:10:09 +01:00
providers.nix fix(calendars.json): Remove failing calendars 2024-01-06 23:51:19 +01:00
README.md readme: update it 2022-03-05 23:19:02 +01:00
rollup.config.js feat(npm): Update dependencies 2024-01-26 11:28:37 +01:00
shell.nix switch to npins and buildNpmPackage 2023-07-23 16:21:13 +02:00

Calendar of all calendars: Metis

This is a meta-calendar where you can declare multiple calendars and aggregate them from multiple trusted sources.

Build Status

Instructions

This project has only a frontend and use reverse proxies to handle multiple calendar sources and avoid CORS issues, only npm or similar is required, then run npm run dev to run the development server.

Warning : You have to run npm start once first.

Deployment

You only need to run npm run build to produce a production bundle you can serve statically, but, do not forget reverse proxies rules, take for example: https://git.rz.ens.wtf/Klub-RZ/infrastructure/src/branch/master/machines/public-cof/nginx.nix#L3-L14.