Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support saving schedules with Kerberos login #47

Open
SuperSonicHub1 opened this issue Sep 12, 2023 · 2 comments
Open

Support saving schedules with Kerberos login #47

SuperSonicHub1 opened this issue Sep 12, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@SuperSonicHub1
Copy link

Schedules can currently only be shared across different machines through taking advantage of the "Share" feature of Hydrant. My current setup is editing a Google Keep note with the URL whenever I edit my schedule, which is hilariously scuffed and error-prone.

This feature, if implemented, would allow a user to save their schedules to a database by logging in with their Kerberos identity, making them accessible across multiple devices. Saving schedules to local storage should still be an option for those who aren't MIT students.

@cjquines
Copy link
Member

cjquines commented Sep 12, 2023

OOF this one is going to need an actual backend, which to be clear hydrant currently does not have.

probably could be integrated into the courseroad backend but im not superfamiliar with how that works; @sipb/courseroad-dev would be more familiar

@psvenk
Copy link
Member

psvenk commented Sep 12, 2023

I believe that the FireRoad server has a mechanism for saving schedules, as the FireRoad app has this functionality. (CourseRoad uses the FireRoad server to store schedules and also does not have its own backend.) Ideally we should aim for interoperability between Hydrant and the FireRoad app, just as CourseRoad interops with the FireRoad app.

This would also entail moving from fireroad-dev to fireroad (prod).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants