You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The complete fix needs a second line. There are a large number of potential issues that each impact only a small portion of the developers. This is one of them. In the short time that I've been looking at Remix, this is the second such issue.
One approach is to try to add to the Dockerfile template for all users. This quickly makes the Dockerfile less approachable.
Another is to detect situations like these and adjust the Dockerfile when the condition is present. And to augment the automatic detection with runtime flags to handle cases that can't automatically be detected. This is the approach fly takes with rails, and over time, a lot of flags have been added. Many of the same situations, such as this one, apply both to Rails and not just Remix but all Node projects.
I get a problem, not related with yours, trying to deploy the indie stack to fly.io because of the line: ENV PORT="8080"
The fly looks for the app on the port 3000
I was able to deploy after changing the port of the Dockerfile to 3000
Have you experienced this bug with the latest version of the template?
yes
Steps to Reproduce
Try to deploy on fly.io
Expected Behavior
Correct deployment
Actual Behavior
Error due to permissons of the entrypoint script.
I found the solution in this thread:
https://community.fly.io/t/unable-to-deploy-generic-remix-indie-stack/12429/2
It is necesary to add the next command before the entrypoint line to give permissons to the start.sh script.
RUN chmod +x /myapp/start.sh
The text was updated successfully, but these errors were encountered: