API stands for application programming interface. I think it would be more friendly for people to use it if there was an interface (a basic plain HTML should be more than enough) to generate a proper calendar URL.

This PR adds a new Dockerfile file. It also adds some new lines to the README.md file (example commands for deploying with Docker).

This PR closes #12.

Signed-off-by: Faiz Jazadi [email protected]

The demo page is currently deployed on Heroku using free Heroku Dynos which will no longer be available soon.

Starting November 28th, 2022, free Heroku Dynos, free Heroku Postgres, and free Heroku Data for Redis® will no longer be available. If you have apps using any of these resources, you must upgrade to paid plans by this date to ensure your apps continue to run and to retain your data. For students, we will announce a new program by the end of September. Learn more at https://blog.heroku.com/next-chapter

To keep the demo running, the instance needs to be deployed somewhere else. Docker seems to be a good way to pack the project and ease deployment.

This PR contains a new feature to allow (SIMASTER API) session reusing. Session reusing is achieved by using the cachelib library (SimpleCache is chosen for simplicity). This PR also include updates to the HTML template and the README.md file.

This PR closes #10.

Signed-off-by: Faiz Jazadi [email protected]

One of the downsides of not storing password/session is the need to log in every time a request to the API is made. This also don't look good in the logged in devices page on SIMASTER.

Caching the logged session is not secure, but having it as an option will be nice (should not be a default setting). This way, some users can let their session token cached and have a more efficient and less floody login history.

This PR essentially contains:

1. A new type parameter from the API to identify what type of calendar events the client wants to fetch
2. A scraper (which adds some new requirements, notably lxml2) to scrape exam events from SIMASTER
3. A new events data processor for two different types of events data (class events and exam events)
4. Major refactor to accomodate the above changes

Fixes: #8

This commit essentially does the following:

• Renamed the directory api_web to web
• Updated wsgi.py (changed import statements)
• Added a homepage that contains a simple form interface
• Added a route that serves the homepage
• Refactor

Signed-off-by: Faiz Jazadi [email protected]

Manually grabbing the events.json file is quite tiring, especially when knowing the fact that Simaster's calendar changes quite often.

This commit converted the whole project. This project is now a web-based app which has an API to grab a specific Simaster account's calendar and return it as an iCalendar file.

Signed-off-by: Faiz Jazadi [email protected]

As simaster.ics uses GET request, and credentials are passed openly, it is definitely a security issue.

It would be helpful if there is some warning in the README.md file telling about the security issue and what could be done to prevent unwanted things.

So far, this project have been able to get in sync with SIMASTER's calendar. But, to make things easier, it would have been very nice to have those events linked with their own meeting link (only if they are online events). I am thinking about two options:

1. To have a separate database that contains a user-curated list of meeting list (or make the API fetch another file that contains the meeting list).
2. Crawl the eLearning page in SIMASTER for links (concern: resource)