aiden
/
mastodon
mirror of https://github.com/mastodon/mastodon
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
9,240 Commits
154 Branches
284 Tags
1.1 GiB
Commit Graph

8 Commits (961789d511ad8742b8bc75d145b3a83ec5d03ad8)

Author SHA1 Message Date
dependabot-preview[bot] 5605b828e5 Bump webpacker from 4.0.7 to 4.2.0 () 
* 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
Eugen Rochko d5bfba3262
Do not test PAM authentication by default () 
* Do not test PAM authentication by default

* Disable PAM tests if PAM is not enabled
Yamagishi Kazutoshi b8f0cfd6e3 Add parallel test processors ()
Alexander 8e88a18316 update gem, test pam authentication () 
* update gem, test pam authentication

* add description for test parameters

* fix inclusion of optional group
Akihiko Odaki c110fa62ac Provide default OTP_SECRET value for development environment ()
Patrick Figel df4ff9a8e1 Add recovery code support for two-factor auth () 
* 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  and fixes 

* Set OTP_SECRET in test enviroment

* add missing .html to view file names
Eugen 157fd07edc Update .env.test
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.