OGKevin / ComBunqWebApp / 101 / 1
88%
master: 88%

DEFAULT BRANCH: master
Ran
Files 43
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 81.553% (-14.7%) from 96.285%
101.1

push

travis-ci

web-flow 
First step for adding BunqAPI (#26)

* generating private key

* Installation script added

Some importing issues
Need to save the installation response

* changing dir

* Installation token gets saved

Later need to make it that the user generates these info and the Token.json and Privatebunq.pem gets downlaoded so the user can store them. These files should then be deleted once the dowload action is complete.

* Using tmp files

using NamedTemporaryFile() to handle the Token and private key files,
this way they get deleted from the server after usage.

created test for installation.py

* basic front end

need to make form to call createKey() and download the files

* basic form created

* File download struggles

Instead of the actual file downloading, it downloads a new file with the file path in it x_X

* temp file is one JSON

downloaded files are empty now -.-

* No tmp files

instead of using temp files, im generating a download file with
the private key and token, so nothing gets stored server side atm.

* file downlaoded is encrypted

need to make them tmp files inseide the tmp dir
Guess we are using tmp files

* Using tmp files, need to delete them after response

* User Pass & https

user can entrie pass, need to genereate an user id and save this with the password.
Need to encrypt this password before saving in db
Added settings to focre HTTPS on heroku

* need to get requireJS

Need to get that module so i can use the uniqID script

* Ok, using RSA & privateKey

not saving these in DB yet. Now instead of generating .enc file it will just be a .json

* preparing for user log in

* Private key is saved

Users must have an account before they can generate a JSON file

* Using AES again x_X

* Generated JSON is encrypted via AES
* Each user gets a GUID to check if the file belongs to this user
* Noting relating to the ecryption is stored in the database

* Added API field... (continued)

504 of 618 relevant lines covered (81.55%)

0.82 hits per line

Source Files on job 101.1