sebastienbarbier / seven23_server Goto Github PK

Current implementation require a database url to a postgres instance.

There is no reason to force the use of postgres and should allow the use of sqlite for easy and quick setup. Such solution would be convenient for CI/CD.

When deploying, a log should display current state of the instance to help user understand it.

It is important to create a travis process to check unittests (not existing yet) and if build is not broken (exising thanks to issue #5)

Currently as integer, should be a float to allow more precise pricing.

Settings refuse to start if storage is undefined as .lower() of undefined does not exist.

elif not DEBUG or os.environ.get('STORAGE').lower() == 'whitenoise':

We are currently staying at 4.1.x to maintain compatibility with PostgreSQL 11.
This ticket is about migrating all dependencies to django 4.2+ and solve issues with postgreSQL 11.
Main reason to keep PostgreSQL 11 is to keep using prod db from hosting provider.
Need to migrate prod to unlock this.

Related to #67

People should be able to install seven23_server from a publicly available image. This will allow easy installation on many system (targeting synology nas)

UID is in base64 but allauth require a base36 instead. Also token seams to be from Django instead of AllAuth. Current implement block user from getting a forgotten password, which is critical

Using env var, currently hard coded to 30, should be 7

Hello,

I installed the client + server version of the application on my machine.

Once connected to the server, I am prompted to create an account and select a currency. When validating, nothing happens.

Nothing appears in the console on the server side.

Despite everything, these errors appear in console. I guess they have something to do with the server's SECRET_KEY variable but I don't see if it needs to be set on the client.

Thank's

This feature will mostly be implemented on client side, but we need to provide an API to store blob data.

When fetching records, we need a way to get only latest modification.
API currently allow to fetch record with a filter on last_edited field but does not provide input if a record has been deleted (like a tombstone).

One common request is adding support for Docker to facilitate deployment 🚀. There is no reason not to do it.

Server code currently use the one command deployment concept, which allow easy build and run on cloud plateform. It seams important to keep this as an option to keep current stack.

Current installation process can be find on seven23_server online documentation

When displaying categories page, allow edit form are initialised as empty.
This is a bug, and should be filled with selected item.

Might be a nice add to have free labels to categorises expenses (for example by event).
Those would be different than categories, and represented by a hashtag and a picture.

Current docker implementation miss some dependencies and does not work out of the box.

This task is about fixing current implementation and improve it so it cover most cases.

• Fix current implementation
• Deploy public image to install on front end CI/CD using docker-compose
• Update documentation with how to use
• Handle new user on creation with docker image (see #24)

Implement a data structure to store recursive transactions.
Need to be tested with unittest.

We should have the serveur URL as an advanced options on the login page in order to use the frontend with any server.

GPRD require the possibility for a user to disable his account without deleting their data.
This feature needs to be implemented.

Using django-rest-framework-bulk.

While trying to install python packages, I had the following error :

ERROR: Cannot install -r requirements.txt (line 3) and docutils==0.16 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested docutils==0.16
    botocore 1.17.16 depends on docutils<0.16 and >=0.10

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

Lowering docutils to 0.15 resolve the error (or maybe upgrading botocore).

Currently using Travis, this ticket is about migrating this repository to Github actions.

Entry point /api/v1/users/email should check if provided value has an email syntax and return appropriate error message otherwise.
Right now, it seams to accept any string without

Current backend crash on POST request using /api/v1/debitscredits as id is expected to be an integer but might be received as string by a wrong request.

It is expected to return 401 bad request instead of 500.

Related to a front end bug : sebastienbarbier/seven23#71

Using rest_auth registration return 204 instead of 201. Looks like after migrating to new version it expect different settings to enable SESSION LOGGING.

Apply security release : Django security releases issued: 4.0.6 and 3.2.14 - https://www.djangoproject.com/weblog/2022/jul/04/security-releases/

We need to be able to get the result of grunt serve with grunt build in order to deploy a production server.

Making the project easily self-hostable is an important goal for this project. After solving technical limitation, it should be possible not to simplify and improve the overall experience. This ticket is about making the installation easier, improving documentation, and mentioning self-hostable instance on seven23_website.

I agree redesign is quite a strong term since we start from northing 🤣.

Apply latest django version to seven23_server.
See django post for details.

User profile has auto_sync set to False by default, should be True

It seems like everything related to django is pretty much broken (I do not have personal experience with django, I tried to fix it myself).

First error when executing python manage.py migrate:

django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.

Second error when executing python manage.py migrate and add something like os.environ.setdefault("SECRET_KEY", "k3-=2r(yq-towhfr-$@am&p%ze_&1!m!n7h2p%6*=fn4nr$=d^") to manage.py:

django.core.exceptions.ImproperlyConfigured: settings.DATABASES is improperly configured. Please supply the ENGINE value. Check settings documentation for more details.

PATCh request on account return 404 not found.

curl 'https://api.seven23.io/api/v1/accounts/85cb16b9-d233-43ca-aa16-7ed4417974c4' -X PATCH -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/113.0' -H 'Accept: application/json, text/plain, */*' -H 'Accept-Language: en-US,en;q=0.5' -H 'Accept-Encoding: gzip, deflate, br' -H 'Content-Type: application/json' -H 'Authorization: Token a...b' -H 'Origin: http://localhost:3000' -H 'DNT: 1' -H 'Connection: keep-alive' -H 'Referer: http://localhost:3000/' -H 'Sec-Fetch-Dest: empty' -H 'Sec-Fetch-Mode: cors' -H 'Sec-Fetch-Site: cross-site' -H 'Pragma: no-cache' -H 'Cache-Control: no-cache' --data-raw '{"id":"85cb1db9-df53-43ba-aa26-7ed4417974c4","preferences":"e...w"}'

Return

* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< Server: nginx/1.21.3
< Date: Wed, 03 May 2023 17:12:16 GMT
< Content-Type: application/json
< Content-Length: 23
< Connection: keep-alive
< Vary: Accept, Origin
< Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
< X-Frame-Options: DENY
< Access-Control-Allow-Origin: *
< Sozu-Id: 01GZH9KD10CSBBNCTQRSJK7WSV
< 
* Connection #0 to host api.seven23.io left intact
{"detail":"Not found."}%

When a user deploy a new server instance, registration is by default disable. This create an issue as admin can't create a user account.

Admin could use superuser as user account but not sure that's a good idea. Would be better to implement an easy way to create the first account.

Currently, the administrator need to enable registration using ALLOW_ACCOUNT_CREATION global variable, create an account, then disable it. This issue is about simplifying that process.

One suggestion could be to implement a wizard and guide the user. This would only be enabled if server instance has just been installer, like having no user account for example.

Could also be an opportunity to improve the UX but providing context / informations.

As part of a front end update, user should be required to confirm his private key at least once. Status of such verification will be stored within a user profile as boolean.

Links point to seven23.io/redoc and seven23.io/swagger but should now redirect to api.seven23.io

There are two small bugs in the installation doc:

• settings.py path ( 723e_server/django_723e/ )
• run client cmd (grunt serve-dev)

Current implementation store autosync preference to account blog. Front-end had an issue with updating local account while being logged ... (sebastienbarbier/seven23#109).
This is a fix now storing auto_sync as a user preference for all accounts. Front-end will apply changes in a future release.