mastodon

Commit Graph

Author	SHA1	Message	Date
dependabot-preview[bot]	5605b828e5	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	5 years ago
Eugen Rochko	d5bfba3262	Do not test PAM authentication by default (#9027 ) * Do not test PAM authentication by default * Disable PAM tests if PAM is not enabled	7 years ago
Yamagishi Kazutoshi	b8f0cfd6e3	Add parallel test processors (#7215 )	7 years ago
Alexander	8e88a18316	update gem, test pam authentication (#7028 ) * update gem, test pam authentication * add description for test parameters * fix inclusion of optional group	7 years ago
Akihiko Odaki	c110fa62ac	Provide default OTP_SECRET value for development environment (#6617 )	7 years ago
Patrick Figel	df4ff9a8e1	Add recovery code support for two-factor auth (#1773 ) * Add recovery code support for two-factor auth When users enable two-factor auth, the app now generates ten single-use recovery codes. Users are encouraged to print the codes and store them in a safe place. The two-factor prompt during login now accepts both OTP codes and recovery codes. The two-factor settings UI allows users to regenerated lost recovery codes. Users who have set up two-factor auth prior to this feature being added can use it to generate recovery codes for the first time. Fixes #563 and fixes #987 * Set OTP_SECRET in test enviroment * add missing .html to view file names	8 years ago
Eugen	157fd07edc	Update .env.test	8 years ago
Alyssa Ross	75d0903317	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

8 Commits (4e524218d3086e4f930e2005f1ce2d82f29e1a20)