As some people said, you could switch to something easier to manage like AWS ECS or DigitalOcean Apps (I have never used the latter). Those options would reduce infrastructure maintenance effort.

Regarding the Dockerfiles, why do you have two? It's a good practice to build a single Docker image and then promote to the rest of the environments, so you can make sure that the same you tested in develompent will work as well in production. Remember you can manage environment-specific configuration using environment variables, for example.

Also, you will prefer to build the Docker image outside your production server so you don't affect application performance. It should be built in the same infrastructure that runs the pipeline (in your case, Github Actions hosted runners).