Having a static website side by side with cloudron vs inside cloudron?
-
I'm just starting to understand how cloudron operates: it takes over sysadmin from a bare system; you don't do any installs on the bare system (like say nginx) and leave it in the hands of cloudron.
My use case is to host a static website (company website, to be done; currently on WP, and we want out
).I know about Surfer.
Is this the way to go? Or should we host the site away from the server that runs cloudron? What are the downsides of using surfer compared to say the same server without cloudron using nginx or apache? I'm a newbie at this, just so you know. The more 'set and forget' the better
-
I'm just starting to understand how cloudron operates: it takes over sysadmin from a bare system; you don't do any installs on the bare system (like say nginx) and leave it in the hands of cloudron.
My use case is to host a static website (company website, to be done; currently on WP, and we want out
).I know about Surfer.
Is this the way to go? Or should we host the site away from the server that runs cloudron? What are the downsides of using surfer compared to say the same server without cloudron using nginx or apache? I'm a newbie at this, just so you know. The more 'set and forget' the better
Compared to 'just doing it yourself' you should way in some factors.
- Do you have a reliable backup solution?
- How much time do you want to invest into hosting?
- Are you able to keep the self hosted site secure? (Including the whole system)
If you want 'set and forget' Cloudron could be the solution for you.
Try it. It's free with the documented limitation.You can have two apps. Surfer / LAMP for your current site (simple migration) but as @privsec recommended migrating your WP to the Cloudron WP App could pay out for even more 'set and forget'.
Give it a shot on a small server with backup setup and then if you want to you can migrate the whole Cloudron to a dedicated big server or start with a scalable solution from the get-go.
-
I'm just starting to understand how cloudron operates: it takes over sysadmin from a bare system; you don't do any installs on the bare system (like say nginx) and leave it in the hands of cloudron.
My use case is to host a static website (company website, to be done; currently on WP, and we want out
).I know about Surfer.
Is this the way to go? Or should we host the site away from the server that runs cloudron? What are the downsides of using surfer compared to say the same server without cloudron using nginx or apache? I'm a newbie at this, just so you know. The more 'set and forget' the better
@qwinter My strong advice : don't do side-by-side - do inside Cloudron.
It's what Cloudron is designed for !
- fastest way to 'get out' of your current arrangements : take WP backup and install on WP inside Cloudron as @privsec says
- then work on static site using Surfer or LAMP
- don't overlook Ghost and Grav as alternatives to WP
Not sure what you want to "get out" of, maybe it's WP, maybe it's hosting plan you have, or a contract with a web developer, or ??. But Cloudron gives multiple options. Just do it inside Cloudron.
-
I'm just starting to understand how cloudron operates: it takes over sysadmin from a bare system; you don't do any installs on the bare system (like say nginx) and leave it in the hands of cloudron.
My use case is to host a static website (company website, to be done; currently on WP, and we want out
).I know about Surfer.
Is this the way to go? Or should we host the site away from the server that runs cloudron? What are the downsides of using surfer compared to say the same server without cloudron using nginx or apache? I'm a newbie at this, just so you know. The more 'set and forget' the better
@qwinter said in Having a static website side by side with cloudron vs inside cloudron?:
What are the downsides of using surfer compared to say the same server without cloudron using nginx or apache
My instinct is to rephrase : what are the UPSIDES of using Surfer ....
But to answer the question, downside of Surfer is it does one thing serve files. Having a server with full range of facilities opens up possibilities (which you may not actually need/want) but significantly also carries management and maintenance. If 'set and forget' is what you prefer, then Cloudron and Surfer/LAMP is much better than having a traditional self-managed server.
And if the question was LAMP on Cloudron vs traditional server, then again the LAMP will almost all of what you would normally do on a normal server without the maintenance headache.
