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

bartoc.org deployment: Handle proxying of bartoc.org/api in Apache #163

Closed
stefandesu opened this issue Mar 8, 2022 · 2 comments
Closed
Milestone

Comments

@stefandesu
Copy link
Member

In order to improve uptime and make access to BARTOC's underlying API a bit more reliable, we should handle the proxying of /api to the backend JSKOS server installation via our Apache web server. Even if BARTOC went down, its API would still be accessible. However, the internal proxying should stay so that the application is not dependent on configuration of an external web server.

Related to gbv/cocoda#670.

@nichtich nichtich added this to the 1.3.0 milestone Oct 14, 2024
@stefandesu
Copy link
Member Author

Since we're not using Apache anymore, but nginx-proxy, we will need this option: https://github.com/nginx-proxy/nginx-proxy/tree/main/docs#multiple-ports-routed-to-same-hostname-and-different-paths

I will test this out and deploy it if it works as expected.

stefandesu added a commit to gbv/coli-conc-server that referenced this issue Oct 15, 2024
stefandesu added a commit to gbv/coli-conc-server that referenced this issue Oct 15, 2024
@stefandesu
Copy link
Member Author

Done!

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

No branches or pull requests

2 participants