bastodon/.gitignore

# 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/

# Ignore Vagrant files
.vagrant/
Initial commit 2016-02-20 22:53:20 +01:00			`# 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`
Adding a Mention model, test stubs 2016-02-25 00:17:01 +01:00			`coverage`
Adding avatars to profile page and statuses 2016-02-28 00:51:05 +01:00			`public/system`
Adding a docker-compose template for running Mastodon easily 2016-03-14 21:39:39 +01:00			`public/assets`
			`.env`
Add .env.test 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. 2016-11-24 18:48:25 +01:00			`.env.production`
Adding React.js, Redux, revamping dashboard 2016-08-24 17:56:44 +02:00			`node_modules/`
Adding sync of follow relationships to Neo4J, accounts/suggestions API 2016-10-14 23:10:07 +02:00			`neo4j/`
Add Vagrant development environment support 2017-01-07 13:22:24 +01:00
			`# Ignore Vagrant files`
			`.vagrant/`