This website requires JavaScript.
Explore
Help
Register
Sign In
izaliamae
/
glitch-soc
Watch
1
Star
0
Fork
You've already forked glitch-soc
0
Code
Issues
Pull requests
Releases
Wiki
Activity
e023acfd00
glitch-soc
/
.env.test
6 lines
86 B
Text
Raw
Normal View
History
Unescape
Escape
Add parallel test processors (#7215)
2018-04-21 15:36:22 -04:00
# Node.js
Bump webpacker from 4.0.7 to 4.2.0 (#12416) * Bump webpacker from 4.0.7 to 4.2.0 Bumps [webpacker](https://github.com/rails/webpacker) from 4.0.7 to 4.2.0. - [Release notes](https://github.com/rails/webpacker/releases) - [Changelog](https://github.com/rails/webpacker/blob/master/CHANGELOG.md) - [Commits](https://github.com/rails/webpacker/compare/v4.0.7...v4.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> * Use NODE_ENV=tests instead of test, to work around async modules not having a chunk
2019-11-20 11:56:11 -05:00
NODE_ENV=tests
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 12:48:25 -05:00
# Federation
LOCAL_DOMAIN=cb6e6126.ngrok.io
LOCAL_HTTPS=true
Reference in a new issue
Copy permalink