Scarica i file del calendario iCal dall'URL di Facebook o dal numero dell'evento. Utilizza un service worker e può essere utilizzata offline e installata come PWA (Progressive Web App). https://mobilizon.it
Go to file
Ondřej Synáček 401ff587e2 set up travis CI 2020-07-15 21:05:25 +02:00
.ebextensions add node command for AWS 2019-11-02 11:30:02 +01:00
docs add preview gif to readmer 2020-01-19 19:40:29 +01:00
lib add specs for LD JSON parser 2020-07-15 20:54:24 +02:00
logs add logger and daily rotating log files 2019-10-24 10:32:01 +02:00
mocks add specs for parser utils 2020-07-15 20:54:24 +02:00
test add specs for parser utils 2020-07-15 20:54:24 +02:00
.gitignore add AWS settings 2019-11-02 11:09:55 +01:00
.travis.yml set up travis CI 2020-07-15 21:05:25 +02:00
package-lock.json add CLI interface made just for parsing 2020-07-15 20:54:24 +02:00
package.json add CLI interface made just for parsing 2020-07-15 20:54:24 +02:00
readme.MD set up travis CI 2020-07-15 21:05:25 +02:00

readme.MD

Build Status

fb2iCal

fb2iCal animated gif of the app

This app allows you to download iCal calendar files from Facebook URL / event number.

You can use it as a service at https://fb2ical.com or use this repository to launch your own instance.

The page that is served by the app uses a service worker and can be used offline and installed as PWA (Progressive Web App).

Development

It can run in environment with NodeJS 10 installed. It does not use Facebook API for retrieving information, instead it relies on crawling and scraping event URL. This means that it can stop working or the results might not be reliable so use this at your own risk.

Run development server: npm run start:dev.

Run development server with debugger npm run start:dev:inspect.

Static assets

There is no clever way to invalidate static assets (HTML, CSS, JS), so if you make any changes, just increment query parameters in view template(s) and service worker. Changing service worker should trigger new update event that should also re-fetch new assets.

Sorry I wanted to keep the app simple so this is done manually. No big deal for me though.

Deployment

The command npm run start will start the server in production mode.

The app can be run as stateless and does not need any persistent storage.

The app is automatically set up to create logs in logs/ directory each day but it's up to your environment if the file system is persisted.

HTTPS

App contains middleware that will redirect all traffic to HTTPS if the requests contain header X-FORWARDED-PROTO. For this to work, the middleware has to be enabled by setting environment variable ENFORCE_HTTPS to value 1.

There are environment variables for setting pu SSL certificate from Let's Encrypt (acme challenge):

  • CERT_ENDPOINT: endpoint without leading slash such as .well-known/acme-challenge
  • CERT_SECRET

This way you can set up the endpoint that will reply with secret and this should allow you to generate key pairs.