What are pros and cons of surfer
-
What are the pros and cons of using surfer compared to sites for static hosting like netlify, vercel or render?
I'm guessing with surfer you don't have a CDN, which could be important. I'm planning to host the company site (converted to static) soon.
I haven't even installed surfer yet
-
What are the pros and cons of using surfer compared to sites for static hosting like netlify, vercel or render?
I'm guessing with surfer you don't have a CDN, which could be important. I'm planning to host the company site (converted to static) soon.
I haven't even installed surfer yet
@qwinter said in What are pros and cons of surfer:
you don't have a CDN
I would say this is the biggest factor. With the services mentioned making the files available is somebody else's job. when you do it through surfer its running on your own server.
I am using it to host a few sites and simple download servers. Websites can either be public, protected by a simple password or require a user on the same cloudron box.
And I can easily automate uploads through the surfer cli in my Drone CI pipeline.
What is not part of surfer, but may be available through the cdn provider may be automatic statistics or forms.
-
@qwinter said in What are pros and cons of surfer:
you don't have a CDN
I would say this is the biggest factor. With the services mentioned making the files available is somebody else's job. when you do it through surfer its running on your own server.
I am using it to host a few sites and simple download servers. Websites can either be public, protected by a simple password or require a user on the same cloudron box.
And I can easily automate uploads through the surfer cli in my Drone CI pipeline.
What is not part of surfer, but may be available through the cdn provider may be automatic statistics or forms.
@fbartels said in What are pros and cons of surfer:
@qwinter said in What are pros and cons of surfer:
you don't have a CDN
I would say this is the biggest factor. With the services mentioned making the files available is somebody else's job. when you do it through surfer its running on your own server.
Also, CDNs are highly critical under GDPR as it results in transfer of personal data to US based providers. For recent decisions: https://www.taylorwessing.com/en/insights-and-events/insights/2021/12/vg-wiesbaden-prohibits-use-of-content-delivery-networks or https://wptavern.com/german-court-fines-website-owner-for-violating-the-gdpr-by-using-google-hosted-fonts
-
FWIW, https://docs.cloudron.io , https://screenshots.cloudron.io are both surfer. For reasonable traffic sites, they work just fine.
In the end, it very much depends on your use case. CDNs make sense if you have many static assets and a very very high traffic website. Google published some study a while ago that people go away if your page takes more than 3 seconds to load. So, that's a good metric to work with.
