Logically, I’d like to be able to use that CDN service, but have my configuration file hosted locally. It’s a shame that the mathjax-latex plugin doesn’t allow the MathJax tree to be served from the default server (what the plugin settings calls the ‘MathJax CDN Service’). This MathJax setup was way easier on the EC2 since the ssh shell allowed for wget and local unzip directly from the apache2 htdocs tree. I did that directory tree transfer with FileZilla since sftp ‘put –r’ appears to be busted. If not, then I may consider changing to another host.Ĭonfiguring a custom MathJax configuration was a bit of a pain with only sftp access, mostly because I had to copy the MathJax tree, which was very slow for so many small files. I’ll see first if only having sftp access to htdocs is enough of a major inconvenience to pay that additional yearly fee.
WOLFRAM CDF PLAYER UPGRADE
It also looks like I can upgrade this to a more generic web hosting environment later if the cost of that seems justified. It is less flexible than a godaddy standalone web-hosting environment, but also cheaper ($12 for the first year, including the domain name, and ~$50/year after that). I ended up deciding to use a go-daddy hosted wordpress instance, which is a flat rate service. I would also have pay separately for a domain name, and pay separately for amazon hosting of the DNS entry. The charts seem somewhat vague, depending on future usage of both machine and storage. However, with an amazon EC2 image, I’m not really sure what I would end up paying.
That’s a flexible setup and offers direct access to the Linux VM, which is very nice.
WOLFRAM CDF PLAYER TRIAL
I tried out an amazon EC2 bitnami image for a while (amazon offers a free trial year to evaluate their offerings). Compared to wp-latex, this “new way” completely kicks ass, and should save me a lot of time. However, once I tried mathjax-latex, I was sold. I’d also wanted to be able to use the wolfram CDF plugin on my blog, but also not enough to pay for it. I’ve wanted plain html hosting for a while, but made do with google sites (i.e. mathjax-latex and wolframcdf), and to also be able to put plain old html and arbitrary file content into the apache2 directory structure.
I wanted the flexibility to be able to manage wordpress plugins (i.e. My primary motivation for this was truly geeky. After 611 blog posts on my old hosted blog, dating all the way back to 2009, I’ve decided to ante-up and pay for more flexible hosting.
0 kommentar(er)
