@Emad-R Exactly, that's more than running your own. $2.95 PER WEBSITE is quite expensive. Run your own and you can do it for $.35 per site!
No you cannot. Not for a single site or even a dozen.
$5 vultr instance / 12 sites comes in at $0.42
That doesn't count the labor to maintain, patch, make resiliant (excluding content related development, etc).
While certainly not expensive, it is also certainly not $0.35.
Ah, but don't forget, when we did a labour study we found that dealing with your own install had lower labour than when dealing with a shared instance because you don't get raw access. So we lowered labour.
So my numbers were obviously without labour, but so were the shared numbers. If you include labour both go up, but the shared goes up more from what we found in testing.
@scottalanmiller why install a proxy when Apaches here and working what is the benefit to having a proxy on the same server. Let’s Encrypt perfectly with Apache
Security and flexibility typically. Here is the admitted marketing material from Nginx on security: "Security and anonymity – By intercepting requests headed for your backend servers, a reverse proxy server protects their identities and acts as an additional defense against security attacks. It also ensures that multiple servers can be accessed from a single record locator or URL regardless of the structure of your local area network."
So if 4th is strictly using RSAT... would 5th be full automation using SCCM, SCVMM, Orchestrator, and App Controller?
Yes, I believe so. Those would be tools in the Microsoft toolset for that. They tend to take a very different approach than many of their competitors and it's been a while since I've used it. Not sure if SCCM goes all of the way to defined state or just really heavily automated forth form. But I think you can get to that state.
I believe it is properly state defined (fifth form) but not code defined like most of the alternatives.
I think I got lost in all the clutter... but why do you separate Remote GUI from Remote CLI ?
Essentially "automatable interface" vs non-automatable interface. Not that GUIs cannot be automated, but effectively they cannot be.