Since the deploy is handled by flyctl is there something like a .flyignore?
Does the CLI take into account .dockerignore files?
Are you ignoring node_modules folders?
2 Likes
When you don’t have Docker running locally, we create a tarball of your working directory and ship it off to our remote builder. This does respect the .dockerignore file: https://github.com/superfly/flyctl/blob/master/docker/build.go#L92
It doesn’t explicitly ignore node_modules, though, anything you want to exclude needs to be listed in .dockerignore.
1 Like
It would be great to mention that in the Node tutorial of the docs.
Do you accept PRs for the docs?
1 Like
Thanks I totally missed it! 
I would have expected it to be higher up in the Docker config.
(You didn’t miss it, I just bumped it in this morning UK time)
The logic of the tutorials is to make a clear path from start to deploy and then to add finesse and optimizations later. Stops the reader being distracted.
Also, thats part of a newer version of that tutorial I’m working on which well, lets say there’s no Dockerfile to build (check out the latest beta of flyctl … I really should make that more prominent for testing folks).
Ahaha thanks for mentioning it. I was doubting myself.
Also, thanks for adding it. 