On Thu, Jul 10, 2014 at 3:30 AM, John Cast <jdc...@stanford.edu> wrote: > I'm in unfamiliar territory with the web stuff, but it sounds so far like I > will generate an HTML doc every time I run my script and then somehow turn > that HTML doc into a static site? (My terminology is weak here I'm sure)
If you go with the static website route, you will have to: (a) generate a reStructuredText/Markdown/HTML file that your static site generator (like Pelican, or Nikola* <http://getnikola.com/>) will turn into a nice, pretty website for you, or (b) just generate one HTML file, skipping the “static site generator” part. > Web - Currently it looks like maybe static HTML page(s) generated every time > my script is run is the right way to go? Yes — it’s generally easier and nicer to do this, unless you were to run your script very, VERY often. > It sounds like I need a server on my desktop? > I need to create a site and host/serve this somehow using my > server? Hosting websites off a desktop can be troublesome. Your computer must stay on all the time (or at least at the times when the website should be accessible), you have to get a static IP, or use a dynamic DNS service, and that’s assuming your ISP won’t hate you for hosting a website. It might be better to use an actual server instead. > I don't need a webframework to do this? If you’re staying with static webpages, then yes. * disclaimer: I’m quite involved with Nikola’s development; however, even with that aside, I believe Nikola is much more human-friendly than Pelican. To each their own, though. -- Chris “Kwpolska” Warrick <http://chriswarrick.com/> PGP: 5EAAEA16 stop html mail | always bottom-post | only UTF-8 makes sense _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor