4 ms·

This seems more difficult than pushing the static files to netlify via GitHub.

• leephillips 5y ago
  I know that it seems so. When I started doing this I think the dominant browser was called “Mosaic”. In the intervening couple of decades I’ve seen many people, who relied on “simpler” solutions, suffer data loss, exploits, sites disappearing when some company disappeared, sites being disappeared because a company decided they violated a TOS or just didn’t like their content, discovering that their articles were being used to track and advertise to their readers, and so on.
  • postpawl 5y ago
    Most of what you said also applies to VPS providers. There are more scalable ways to host static files without needing to maintain a VPS. You could also move to S3 + cloudfront if you had issues with netlify. I’ve had 0 issues with netlify for years though.
    • leephillips 5y ago
      I realize that, and there may be no rational reason for you to switch to a setup like mine. But, aside from avoiding such things as Wordpress exploits, my approach turned out to have other advantages. Over the years I added to my knowledge and taught myself how to provide things other than static files. Today my readers can use gnuplot in a Jupyter notebook, and interactive Pluto¹ notebooks backed by Julia running on a VPS. No canned solution exists for this, and in fact I had to work with the Pluto developers to iron out some kinks. This is only possible because I have total control over the servers. If you know will only ever want to serve static files, there are simpler options (with potential pitfalls). But those options are also limiting, in case one day you want to do something unusual. [1] https://github.com/JuliaPluto/PlutoUI.jl https://github.com/JuliaPluto/PlutoUI.jl