Ah yep... tough sell...
What we've done to get around that is setup our own VPS that we essentially use
as a shared host for our low/mid traffic sites that don't want their own VPS.
That way, they are set up exactly how we want them, we can control the web root
etc and control the installed libs.
Then the price is split over the customers that are on it which at least covers
the cost once you have 2+ clients on it.
Would recommend Sitehost for that setup.
Cheers
Craig
Craig Boxall Director
P / 09 550 3084
M / 021 564 522
E / [email protected]
W / PIXELFUSION.CO.NZ / WHERE DESIGN & DEVELOPMENT FUSE
A / SUITE 2.1, 8A CLEVELAND RD, PARNELL, AUCKLAND / PIXEL FUSION LTD, PO BOX
311 022, GLENFIELD, NORTH SHORE CITY, 0747 / MAP
On 23/01/2012, at 9:08 AM, Jochen Daum wrote:
> Hi Craig,
>
> thanks for the quick response
>
> We had a few clients that insisted on hosting their Symfony site on a shared
> host. For the most part we have transitioned them off to VPS'.
>
> We still have this one though which we inherited when the old dev moved on
> http://www.bridaldesign.co.nz/
>
> Seems to behave ok. Only issue we find a real pain in the ass is that most of
> the time, you can only write to the webroot of a shared host so we had to
> invert the structure of the project so that the Symfony app files were inside
> the web root. Not a major but not ideal as you have to mess around with
> making sure that someone can't browse to the database.yml etc
>
> Not sure why you're asking for examples... hopefully it's to convince a
> customer to host on a VPS :)
>
> Unfortunately the reason is cost cutting, so the convincing wasn't enough.
>
> Many thanks, Jochen
>
> --
> NZ PHP Users Group: http://groups.google.com/group/nzphpug
> To post, send email to [email protected]
> To unsubscribe, send email to
> [email protected]
--
NZ PHP Users Group: http://groups.google.com/group/nzphpug
To post, send email to [email protected]
To unsubscribe, send email to
[email protected]
