ae142ab32a
It took me ages to get Mastodon set up with the tests passing because the environment variables I needed to define weren't documented and I had to work them out one at a time. This change adds a .env.test file, and makes it so it isn't ignored by git. I think it makes sense for the .env.test file to be in git, since there's nothing secret in it, but other approaches would be to have a .env.test.sample (like the corresponding one for production), or to set these values in a test helper, or to adapt the tests to work with environments other than this one. I'd be happy to make these changes if that would be preferred. Being able to get set up and run the tests is a pretty important part of being able to contribute to Mastodon (or your test coverage with suffer!), so having some sort of solution like this one is vital.
24 lines
553 B
Text
24 lines
553 B
Text
# See https://help.github.com/articles/ignoring-files for more about ignoring files.
|
|
#
|
|
# If you find yourself ignoring temporary files generated by your text editor
|
|
# or operating system, you probably want to add a global ignore instead:
|
|
# git config --global core.excludesfile '~/.gitignore_global'
|
|
|
|
# Ignore bundler config.
|
|
/.bundle
|
|
|
|
# Ignore the default SQLite database.
|
|
/db/*.sqlite3
|
|
/db/*.sqlite3-journal
|
|
|
|
# Ignore all logfiles and tempfiles.
|
|
/log/*
|
|
!/log/.keep
|
|
/tmp
|
|
coverage
|
|
public/system
|
|
public/assets
|
|
.env
|
|
.env.production
|
|
node_modules/
|
|
neo4j/
|