-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
Failing to get Mercure Hub up and running in Platform.sh #940
Comments
I've got around the read-only issue concerning the bolt database by doing a number of things. Here they are:
Here's the resulting applications.yaml,
The problem that I now have is a HTTP 502 error. Specifically, my project is configured such that mercure (or caddy) is not listening at the same place that nginx is set as stated in troubleshooting development (http responses 502 bad gateway). Interestingly, ChatGPT suggest that I set the
However, when consulting [Upstream] reference on platform.sh docs, I see no provisions to perform such a configuration. In other words, this is not compilable and legal. So, how do I get platform.sh to navigate to the port that mercure is running on. This is no longer a mercure issue but a platform.sh problem. [Closing issue on mercure Github repo] |
I have the following applications.yaml configured in a Symfony app,
The mercure binary downloads but when it is run, I get the following error,
I've created a mount that should be writable. I'm not sure what I have not configured right
The text was updated successfully, but these errors were encountered: