This website works better with JavaScript.
Home
Explore
Help
Sign In
nekobus
/
mastodon_neko
forked from
closed-social/mastodon
Watch
1
Star
0
Fork
0
Code
Issues
0
Pull Requests
0
Projects
0
Releases
0
Wiki
Activity
闭社主体 forked from
https://github.com/tootsuite/mastodon
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
6945
Commits
2
Branches
112 MiB
Tree:
94e5e834f2
closed-social-v3
master
v0.1.2
v0.1.1
v0.1.0
Branches
Tags
${ item.name }
Create branch
${ searchTerm }
from '94e5e834f2'
${ noResults }
mastodon_neko
/
.env.test
5 lines
85 B
Raw
Normal View
History
Add parallel test processors (#7215)
6 years ago
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.
8 years ago
# Node.js
NODE_ENV=test
# Federation
LOCAL_DOMAIN=cb6e6126.ngrok.io
LOCAL_HTTPS=true