Error during deployment in Fly.io, Dockerfile needs to give permissons to `start.sh` script about indie-stack

[MichaelDeBoey]

CC/ @rubys

[rubys]

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.

This is why I'm encouraging Remix to converge with fly on a single dockerfile generator.

[felipeLx]

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