http://archive.org is another gigantic free repository. They already have a comments system built into their pages. I don't know how it works. It might be worth checking out.
Both these organisations are free and are aimed at helping make content available to the community which might otherwise be lost. You have complete control over the look of webpages at ibiblio.org because you simply upload static pages.
I don't know how much control over the look archive.org provides because everything is dynamically served from xml data, I think. It might be possible to add static content, I don't know.
But both are free, permanently available, and have excellent security.
Cheers,
- Miriam
Peter Shinners wrote:
Gitlab also has great static site support for free, and you can use custom domains. They also make it easy to run most static generation tools as a CI job. Although part of me thinks just pushing the static content is easiest. It sounds to me like there's a list of acceptable hosting choices that won't cost anything.Keeping the games list as a feed from other service sounds like it has the best chance of working.On 12/17/2016 10:51 PM, Lenard Lindstrom wrote:Bitbucket also has static web site support. I set one up for the Pygame docs awhile ago, but have not maintained it:http://pygame.bitbucket.org/docs/pygame/ The repository is here: https://bitbucket.org/pygame/pygame.bitbucket.org Lenard Lindstrom On 16-12-17 09:16 PM, Daniel Foerster wrote:You know, I suppose we could just use GitHub pages.On Dec 17, 2016 17:32, "Charles Cossé" <ccosse@xxxxxxxxx <mailto:ccosse@xxxxxxxxx>> wrote:On Sat, Dec 17, 2016 at 4:12 PM, Daniel Foerster <pydsigner@xxxxxxxxx <mailto:pydsigner@xxxxxxxxx>> wrote: Using S3/CloudFront is a lot cheaper than the EC2 setup you're imagining (and which a Django stack would require). I never said to use Amazon at all. Just use the current server, whatever it is (unless it's Amazon). On 12/17/2016 05:11 PM, Charles Cossé wrote:Yikes! who's gonna pay the Amazon bill? On Sat, Dec 17, 2016 at 4:09 PM, Paul Vincent Craven <paul@xxxxxxxxxxxxxxxx <mailto:paul@xxxxxxxxxxxxxxxx>> wrote: If most of the site is static, then I think Django would be overkill. The static portion of the site can easily be deployed via Amazon S3/CloudFront and then we'd not have to maintain a server. Paul Vincent Craven On Sat, Dec 17, 2016 at 5:00 PM, Charles Cossé <ccosse@xxxxxxxxx <mailto:ccosse@xxxxxxxxx>> wrote: On Sat, Dec 17, 2016 at 3:26 PM, Thomas Kluyver <takowl@xxxxxxxxx <mailto:takowl@xxxxxxxxx>> wrote: So far, I think the proposals for the static information part of the site are Nikola (a static site generator oriented around blogs) and Sphinx (oriented around docs). Both are written in Python. Does anyone want to make the case for any other system? Can Django factor-in there? I guess it would reside underneathe the other pkgs ... but might as well run Python through-and-through imho. -- Linkedin <https://www.linkedin.com/in/charles-cosse> | E-Learning <http://www.asymptopia.org>-- Linkedin <https://www.linkedin.com/in/charles-cosse> | E-Learning <http://www.asymptopia.org>
-- There are two wolves and they're always fighting. One is darkness and despair. The other is light and hope. Which wolf wins? Whichever one you feed. -- Casey in Brad Bird's movie "Tomorrowland"