dachary
/
dashboard
forked from Hostea/dashboard
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
204 Commits
5 Branches
0 Tags
4.9 MiB
Commit Graph

14 Commits (3019d9d73978222b56afe496f57e519a116e56a2)

Author SHA1 Message Date
Aravinth Manivannan a95158f3df
fix: Gite credentials email: fix subject and let user know instance is 
being provisioned

fixes: https://gitea.hostea.org/Hostea/dashboard/issues/44
 2022-07-09 10:54:45 +05:30
Aravinth Manivannan b12cc044da
fix: Invoice generation must not consider deleted VMs' names for 
checking if payment is already fulfilled

DESCRIPTION
    Invoice generation is dependent on instance_name. Deleting a VM
    doesn't delete the corresponding payments record since payment
    receipts should be preserved for accounting purposes.

    But being heavily dependent on instance_name, without taking deleted
    VMs into account produces incorrect behavior under certain
    circumstances: if a VM named 'foo' is paid for and is deleted before
    its billing cycle is competed and a new VM is created with the same
    name, either by the same user or a different user, invoice won't be
    generated for the new VM since a payment record already exists for
    that billing cycle for the VM named 'foo'.

    Marking deleted VMs' payment records unsuitable for checking if a VM
    is already paid for will result in correct behavior.

fixes: https://gitea.hostea.org/Hostea/dashboard/issues/38
 2022-07-08 22:28:39 +05:30
Aravinth Manivannan bebf18946a
fix: re-enable billing app tests 
Commented out for debugging, forgot to enable(!!)
 2022-07-08 19:31:06 +05:30
Aravinth Manivannan 2c8a5909cb
fix: generate absolute URI when attaching links in invoice and payment 
notification

fixes: https://gitea.hostea.org/Hostea/dashboard/issues/37
 2022-07-08 18:51:04 +05:30
Aravinth Manivannan 2ee54a71e3
feat: management command to periodically generate invoices 
SUMMARY
    `python manage.py generate_invoice` generates invoices for VMs when
    it enters a new billing cycle and sends a notification email to
    VM owners.

    This command should be run as frequently as desirable. Running daily
    is recommended.

BILLING CYCLE
    By default, a billing cycle is 30 days.
 2022-07-08 01:46:17 +05:30
Aravinth Manivannan 438e34f7d6
chore: refactor invoice generation into a util fn 2022-07-08 00:51:11 +05:30
Aravinth Manivannan 9c239ad78b
feat: send invoice generated notification email and payments receipt mail 2022-07-07 20:51:33 +05:30
Loïc Dachary ed0186912d
s/ammount/amount/ 2022-07-03 15:01:09 +02:00
Aravinth Manivannan 8fc20d16be
feat: ues separate fleet repo for each unit test 2022-07-01 19:54:15 +05:30
Aravinth Manivannan 8be1e02a21
feat: load footer ctx in all templates 2022-06-30 14:37:49 +05:30
Aravinth Manivannan 5ec87c83ec
feat: redirect user after successful payments for VM creation 2022-06-29 00:22:49 +05:30
Aravinth Manivannan ec49caa973
feat: payment status checking util 2022-06-25 16:27:43 +05:30
Aravinth Manivannan e688528fa3
fix: check payment status on instance level, used to be user level 2022-06-25 16:27:26 +05:30
Aravinth Manivannan d470033429
feat: implement billing with stripe 
SUMMARY
    PAYMENT WORKFLOW
	1. User is redirected after a new instance is created into a view
	   that generates invoice. There are checks in place to ensure
	   invoices are not generated twice for the same VM. There is also a
	   check in place to generate invoices for time periods that are
	   already paid for
	2. User is redirected to payment form
	3. Stripe takes over
	4. If payment is successful, user is redirected to success page
	5. If payment failed, user is redirected to failure page

    PENDING INVOICES
	The user can see pending invoices on their dashboard

    PAYMENT RECEIPTS
	The user can see payment receipts on their dashboard
 2022-06-22 00:37:03 +05:30