-
Notifications
You must be signed in to change notification settings - Fork 5
deploy the Django app #29
Comments
Could you elaborate a bit more on the security issues with cookies? I was thinking of integrating with inside.gratipay.com, like http://inside.gratipay.com/finances, but maybe that's not feasible? That said, no problem with a new domain. BTW where do you get quote? Godaddy shows some different prices. |
Our registrar is iwantmyname.com. Once we have some financial reporting in place we can revisit that vendor decision if we want to. ;-)
Searching for "security cookies" on this repo turns up gratipay/inside.gratipay.com#593 (comment), which points to a post that gives some further details. |
The cheapest |
If we go back to Xero then maybe we can get away with monthly financial reports (balance sheet and income statement) as PDFs hosted on inside.gratipay.com like we talked about a while back. @nobodxbodon Would that give you the drill-down you are looking for? |
@nobodxbodon Good point. Still, setting up maintainable books in the first place is the hard part here. :) |
I thought doing book-keeping is independent of the software we use (ledger or xero). Maybe I'm missing your point? |
Where is the app that needs to be deployed? How about a static site generated on Netlify for now? |
This is moot with #35. |
Most important follow-on from #28 ... what domain should we use? :-)
We don't want to use a subdomain of
gratipay.com
, because that exposes us to security issues related to cookies. These are available:gratipay.accountant
gratipay.finance
gratipay.financial
gratipay.money
The text was updated successfully, but these errors were encountered: