9 Commits

Author	SHA1	Message	Date
Pēteris Caune	45078e6566	Set the SECRET_KEY default value back to "---" ... Previously, I had changed the default value to "", to force users to set the SECRET_KEY value (the app refuses to start if SECRET_KEY is empty). The problem with that is, out of the box, with the default configuration, the tests also don't run and complain about the empty SECRET_KEY. So, a compromise: revert back to the default value "---". At runtime, if SECRET_KEY has the default value, show a warning at the top of every page.	2021-01-28 15:38:14 +02:00
Pēteris Caune	cdfc9840a7	Source formatted with Black	2019-05-15 14:27:50 +03:00
Pēteris Caune	0ece2664ac	Show a warning when running with DEBUG=True. Fixes #189	2018-11-06 10:48:59 +02:00
Pēteris Caune	9cbd0138da	Demo checks shown on welcome page are not saved to database. User's first check is created when creating the user.	2018-06-14 23:42:39 +03:00
Pēteris Caune	965accaedb	REGISTRATION_OPEN setting. superuser accounts by default have team access enabled. Fixes #97 and #113	2017-02-24 15:58:11 +02:00
Di Wu	fe72792fd2	use basetestcase for most test cases that require predefined user, add test for ensuretriggers, add travis cache	2016-01-18 01:02:42 -08:00
Di Wu	5c1d21f91e	make welcome code logic resilient	2015-11-15 16:10:51 -08:00
Pēteris Caune	d415f42afc	Fix tests	2015-07-01 20:13:19 +03:00
Pēteris Caune	4057759df6	Setting up tests	2015-06-25 22:29:19 +03:00