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.

Sign up for GitHub

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

Jump to bottom

make backend domain name/location configurable #37

Open

2 tasks

MoralCode opened this issue Jan 21, 2024 · 0 comments

Milestone

General Usability

Owner

MoralCode commented Jan 21, 2024 •

edited

Loading

currently the frontend is hardcoded to use the api.classclock.app domain name for fetching schedule data.

this is a problem for people that want to host the app themselves on their own domain.

Implementation ideas: possibly use an env var or superadmin setting (future) or something

Can ClassClock run without a domain? if so what should the default configuration be (maybe assume the API is on a specific port at the same location as the frontend)?
What are the CORS rules? does the backend need to be on the same domain? The backend probably needs this too in order to give the right CORS exception data

MoralCode added this to the General Usability milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment