Question about scm with liveview

Phoenix Forum Questions / Help
,
1

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?

2

standard .gitignore from the mix phx.new

# The directory Mix will write compiled artifacts to.
/_build/

# If you run "mix test --cover", coverage assets end up here.
/cover/

# The directory Mix downloads your dependencies sources to.
/deps/

# Where 3rd-party dependencies like ExDoc output generated docs.
/doc/

# Ignore .fetch files in case you like to edit your project deps locally.
/.fetch

# If the VM crashes, it generates a dump, let's ignore it too.
erl_crash.dump

# Also ignore archive artifacts (built via "mix archive.build").
*.ez

# Ignore package tarball (built via "mix hex.build").
liv-*.tar

# If NPM crashes, it generates a log, let's ignore it too.
npm-debug.log

# The directory NPM downloads your dependencies sources to.
/assets/node_modules/

# Since we are building assets from assets/,
# we ignore priv/static. You may want to comment
# this depending on your deployment strategy.
/priv/static/
2 Likes
3

Makes sense. Thanks!