This is kind of a meta-question about live view. I’m trying to figure out what in my live view source code tree I need to commit to git. It looks like there are a lot of files like assets/node_modules/…/log0000 that get produced at runtime, but aren’t really source files. Others that are a little grayer area are files like priv/static/css/app.css that appear to be generated.
Any guidance as to the best strategy?
standard .gitignore from the
# The directory Mix will write compiled artifacts to.
# If you run "mix test --cover", coverage assets end up here.
# The directory Mix downloads your dependencies sources to.
# Where 3rd-party dependencies like ExDoc output generated docs.
# Ignore .fetch files in case you like to edit your project deps locally.
# If the VM crashes, it generates a dump, let's ignore it too.
# Also ignore archive artifacts (built via "mix archive.build").
# Ignore package tarball (built via "mix hex.build").
# If NPM crashes, it generates a log, let's ignore it too.
# The directory NPM downloads your dependencies sources to.
# Since we are building assets from assets/,
# we ignore priv/static. You may want to comment
# this depending on your deployment strategy.