Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create lokun-billing #19

Open
benediktkr opened this issue Sep 28, 2014 · 2 comments
Open

Create lokun-billing #19

benediktkr opened this issue Sep 28, 2014 · 2 comments

Comments

@benediktkr
Copy link
Owner

After almost 1.5 years, Lokun has grown and so has lokun-record. It is time to split it up into two projects, lokun-record for the RESTLike API with users and nodes, and lokun-billing for everything billing related.

@benediktkr
Copy link
Owner Author

##Things that would be moved

model.py

  • Deposit object
  • BTCAddr object. The new lokun-billing would keep a record of username and BTC addr pairs

Database

  • Table btcaddrs if BTCAddr is moved
  • Table paymentbot
  • Table deposit

Files

  • Bankmail.py
  • dalpay.py, encryption.py and hashing.py need to be copied over, but maintained in lokun-record (save for some git magic)
  • exchanges.py and update_btcprices.py if lokun-billing should keep track fo BTC prices (not sure)
  • paymentbot.py but is deprecated
  • mailchecker.py

Changes in lokun-record

restapi

  • Add POST /user/<username>/deposit or POST /user/<username/credit_isk that requires key auth from a key starting with payment- or billing-
  • Add GET /user/<username>/user1 to create the user1 string in our DalPay protocol. Requires user auth. Maybe the entire DalPay object will be created in record. This functionality is now in lokun-site, but I want this code to be part of lokun-record and that way the site can go back to being a dumb site again

@benediktkr
Copy link
Owner Author

ZeroMQ!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant