On Fri, Mar 29, 2013 at 6:55 AM, Richard Hipp <d...@sqlite.org> wrote: > Suppose I did write my own hosting system. What is is required for that. > (James, you have the most experience with this question, so your input is > especially encouraged!) > > (1) Some means for people to create accounts
There are many schemes. BTW, you should consider Mozilla's BrowserID authentication scheme. > (2) Some means for people to upload Fossil repositories to hosted Create empty repos and then push to them. > (3) Per-account bandwidth tracking? Would you charge for bandwidth? If not don't bother tracking it. > (4) Require advertising (example http://system.data.sqlite.org/) for > unpaid accounts? Sure. > (5) Require unpaid accounts to be open-source? Other repo hosting sites tend to charge according to how many private repos you have. You could offer 1-3 private repos for free + a size limit on the repos, then charge for anything beyond that. > (6) Some mechanism to accept payment for private or add-free accounts? Yes, if you'll charge at all. > (7) Procedures to deal with DMCA takedown requests? Speak to a lawyer about that. > What else is needed? James, what are your bandwidth, cpu, and disk space > requirements? (You can send me that via private email if you prefer.) Egor Homakov had a great blog post[0] about the need to have separate origins for the domain where users login to manage their data, and the domains where user pages can be viewed. I.e., using chiselapp.com as an example, you need two domains: chiselapp.com and chiselapppages.com, with the former hosting only the fossil services and any additional web interfaces, and the latter hosting the web view of user fossil repos. [0] http://homakov.blogspot.com/2013/03/hacking-github-with-webkit.html Nico -- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
