| Age | Commit message (Collapse) | Author | Files | Lines |
|
* Use a hashed password for ADMIN_PASSWORD
A generate_password_hash manage.py command is provided
Fixes #233
* Print a console warning for users using a clear text ADMIN_PASSWORD
* Reword ADMIN_PASSWORD doc
* Update changelog
* Update CHANGELOG.rst
- say it out loud
- bump to 2.0 (that's the logic of semantic versioning while introducing breaking changes)
* Bump to 2.0 (breaking change)
* Update hashed password warning message
* Mention the generate password hash in the Changelog
|
|
|
|
The wsgi file needs to live in the budget dir
if we want it to be installed by setuptools
|
|
Fix navbar responsiveness on mobile.
|
|
* Add a @requires_admin decorator
It can be used to protect specific endpoints with ADMIN_PASSWORD
(a password that is stored unencrypted in the settings)
The decorator has no effect if ADMIN_PASSWORD is an empty string (default value)
* Require admin permissions to access create project endpoint
When ADMIN_PASSWORD is not empty, project creation form on the
home page will be replaced by a link to the create project endpoint
so one is able to enter the admin password before filling the form
|
|
When set to False (True by default), it deactivates
the demo project
|
|
Default settings from app's root path are loaded first
Settings are then overriden by /etc/ihatemoney/ihatemoney.cfg
or by another file which path is set in an env var
Fixes #187
|
|
* Move tests to budget.tests
Update tox.ini to call the unittest dicovery module
Closes #196
* Fix typo in Readme
|
|
Removes py3-only warning (this alias might be removed in future py3 version):
> DeprecationWarning: encodestring() is a deprecated alias, use encodebytes()
> ('%s:%s' % (username, password)).encode('utf-8')).decode('utf-8').replace('\n', '')
py2-compatible change.
|
|
Using new-style flask extensions imports.
grep tells me there were the only flask.ext.* occurences remaining in ihatemoney code.
|
|
It is a bare alias of StringField (thus, no alembic migration is required),
deprecated since wtforms v2.0 (2013).
Removes the following warning:
> DeprecationWarning: The TextField alias for StringField has been deprecated and will be removed in WTForms 3.0
Ref https://github.com/wtforms/wtforms/commit/f07729dd45c0f5191f131d37adb0456104dc7c44
|
|
See also https://github.com/lepture/flask-wtf/pull/287
|
|
That noisy warning was everywhere in our test/CI logs before that commit:
> ./home/travis/build/spiral-project/ihatemoney/.tox/py27/lib/python2.7/site-packages/flask_sqlalchemy/__init__.py:839: FSADeprecationWarning: SQLALCHEMY_TRACK_MODIFICATIONS adds significant overhead and will be disabled by default in the future. Set it to True or False to suppress this warning.
>
> 'SQLALCHEMY_TRACK_MODIFICATIONS adds significant overhe
|
|
Use app.root_path instead of __HERE__
|
|
Note that py3.4 is the version shipped in current Debian version (Jessie).
|
|
|
|
|
|
Remove unused archive feature
|
|
The archive table is not removed from the database model
because it would involve a tricky migration
fixes #170
|
|
|
|
Flask-wtf>=0.13 is now required and Form is replaced by FlaskForm
Py2/3 compatibility is assured by six
|
|
|
|
|
|
Bills and transactions can now be exported to json or csv
ref #28
|
|
ref #173
|
|
Checking item was broken when clicking on the label instead of the checkbox
|
|
|
|
Fix #173
Rewrite multi select widget as a template in order to have all values properly escaped.
|
|
WIP: Upgrade to bootstrap 4
|
|
|
|
Fix a regression introduced with BS4 update.
|
|
Allowing the modal to extend; thus "natural" page scrolling allows to see the
whole popup.
|
|
Actually switching to maintained fork at
https://github.com/uxsolutions/bootstrap-datepicker ; the original project
being unmaintained since 2012.
- Works with recent jQuery
- BS4 is not supported by bootstrap-datepicker, but actually, it works :-)
ref https://github.com/uxsolutions/bootstrap-datepicker/issues/1670
|
|
- modal classes and hierarchy changed since BS2
- striped tables are now handled by css3 pseudo-class rather than classes
- fix placement/alignment for the button and comment above the table
|
|
BS4 provides larger touch-friendly controls anyway.
|
|
Trying to keep same look'n'feel.
|
|
Also fixed some weird alignment issues.
I think this will need more work later (revamp the navbar layout to avoid that
sensation of thing which are floating at random places in the navbar).
|
|
There was no label, which is bad for accessibility.
|
|
|
|
- Adapt to BS4 class names and hierarchy
- Redesign some forms to have the label above the input (mobile-friendly)
- For the remaining inline form (add bill), use the grid, as BS no longer
provides inline form alignment helpers
|
|
|
|
|
|
|
|
|
|
Test was Ok but failed due to some floating point errors.
|
|
Fix ServerTestCase.test_unprefixed test
|
|
Optimise sql queries
|
|
Fix zero-amount transfers and other rounding issues
|
|
The test was always failing, actual reason is the `app.run.configure()` fails
to reset the `APPLICATION_ROOT` setting which `ServerTestCase.test_prefixed`
overloads (side effect).
This patch *do not* fix app.run.configure as it seems uneasy, but takes a
different approach which has the advantage of making the test more explicit.
Would still be a good thing to investigate more on configure().
Fix #163
|
|
A user with a "0.00" balance would have either a "+0.00" in green or a
"-0.00" in red, depending on the exact value of the floating-point value.
Fix this by simply rounding to 2 digits before comparing to zero.
|