Static HTML stack
We'd quite like the ability to specify a HTML-only stack with PHP disabled and no database. While this might seem an odd request, we sometimes have the need for temporary holding sites, additional sub-sites, etc. It's potentially also of use with headless CMS sites. Having related sites on the same server / within the same interface is useful.
While I realise we can use the PHP install for this, I'd prefer something that has code execution properly disabled from the start.
-
Helder Luis commented
2024!
-
Johnny Vernin commented
2023...
+1 -
Simone Ferrara commented
A static site generator (Hugo, 11ty, Astro, etc.) would be great. Many developers are considering headless CMS or SSG due to their excellent performance and better security.
-
Franz Berliner commented
This is probably not going to happen right?
-
Hunain Kapadia commented
Any update on this? much needed
-
Giobi Fasoli commented
A static site generator would be a wonderful thing.
Let be a staging domain with a CMS (wordpress or else), where I can generate the site.
Then a static space and public domain where the site is server with cached html files.
The export could be routined hourly, daily or on demand. The site could not have dynamic actions (forms etc) or maybe you could set some kind of api connection for that.
This would be stunningly useful for me, and it would save a lot of resource on high traffic sites.
Doing this on command line it's a single command (that I stole from github)
wget -k -K -E -r -l 10 -p -N -F -nH http://website.com/
and it can probably be implemented on a .sh file very quickly already -
Anonymous commented
Yes please, for JAMstack deployments similar to Netlify would let us manage our WordPress and headless CMS projects in one place.
-
Webmaster Cuatromedios commented
And use the official HTML5 logo please https://es.wikipedia.org/wiki/HTML5#/media/Archivo:HTML5_logo_and_wordmark.svg
-
Gareth commented
+1
-
GR commented
Is this going to happen or what??
-
Justin commented
+1
-
Anonymous commented
Another vote for this. I can't imagine there are downsides. And what could be simpler to implement?
-
DW commented
Long overdue
-
Paul commented
This needs to happen. I have a few customers with static HTML sites and, currently, I'm having to use another shared host for them. I would much rather get them all over to CW.
-
DMeechan commented
Not sure why this still hasn't been added after 1.5 years. Seems relatively straightforward to implement and would be really helpful to many of us.
-
Ryan commented
Why are you still thinking about this?! I need somewhere besides GitHub to host all the Pixelarity templates I create for clients!
-
Sumit commented
Yes! That's it. I'm also looking for the same functionality.
-
Anonymous commented
Yes, this is exactly what I was looking for. A simple static webhosting managed by Cloudways.
-
Russell commented
There is a nifty little trick with static apps that can speed WordPress websites up a little. It involves
a special type of static app that uses a symlink to point a website subfolder to this static app. When I was hosting with Webfaction, they would allow me to do this.The idea is that you can make the uploads folder of WordPress (/wp-content/uploads) a symlink to a static app. The WordPress uploads folder only has static resources like images and PDF documents, making it a perfect use-case for a static app. I know I would appreciate the performance gains from the reduced overhead in serving these static resources. Also, I don't know if this applies, but if the default configuration gzips images, that would harmful for performance as well -- jpegs and pngs are already compressed, so gzipping them is only wasting computing power and time.
If it's useful, you can find the documentation Webfaction created for speeding up requests to the uploads folder by using this technique on their platform at https://docs.webfaction.com/software/wordpress/advanced.html
TL;DR
A symlink that places a website's images folder in a static app would increase performance.Edit: Actually since Cloudways already uses Nginx to deliver static assets, there might not be any overhead to delivering static HTML files inside of a PHP app.
-
Linda commented
I also think it would be phenomenal if we could host static websites :)