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

Remove public access to API routes #71

Open
helicalbytes opened this issue May 3, 2022 · 0 comments
Open

Remove public access to API routes #71

helicalbytes opened this issue May 3, 2022 · 0 comments
Labels
api Issues relating to the API server component deployment Issues about the production server website Issues relating to the Website component

Comments

@helicalbytes
Copy link
Contributor

On server we can access the api app using its container name as hostname.

The only API endpoint the client website currently uses is the calendar one.

If we create an endpoint in the website which proxies to the API one, then we can remove a need for public API access.

Steps:
(1) Create a proxy endpoint in the website project for the calendar endpoint;
(2) Replace client side calls to use this endpoint;
(3) Don't expose port 3001 in the api container.

@helicalbytes helicalbytes added api Issues relating to the API server component website Issues relating to the Website component deployment Issues about the production server labels May 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Issues relating to the API server component deployment Issues about the production server website Issues relating to the Website component
Projects
None yet
Development

No branches or pull requests

1 participant