set up a VM (or container) on your PC of whatever Linux distro your host is using.
Not every shared hosting provider uses Linux. There are others that use one of the BSDs, SunOS/Solaris was and perhaps still is in use, and some really tough people provide(d) shared hosting on Windows.
And regarding Linux: Debian, SuSE, RedHat, Gentoo, Arch Linux and their derivates should be quite common, but some providers also use other distributions or home-grown systems, some based on Linux From Scratch, some based on Nodereaper-knows-what. You need to reconstruct that system in the VM, including the libraries found on the hosting system.
As a rule of thumb, expect the unexpected when using shared hosting. Don't be surprised to find really old and unmaintained systems running on refurbished or reused hardware. Expect really strange configurations, and workarounds stacked on older workarounds. And especially: Don't expect that the provider has a working backup system for shared hosting.
Yes, there may be shared hosting providers with streamlined, well-maintained systems running on top hardware, and with good backups. But they can't be cheap.
Alexander
--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
| [reply] |
set up a VM
That is probably an excellent idea...
Although it is quite a faff and probably not worth the effort as Perl 5.16 will do everything I need it to do - although it would be nice to be able to strip here doc spaces!
Before long I will need to put in some time and effort to arranging either a VPS or dedicated server although I probably cannot currently justify the cost of the latter.
Part of me is resisting making that move because of the extra possibilities to break things with my very limited knowledge of a Linux environment.
| [reply] |
I wonder if copying the compiler binary to your home-dir and changing its restricted permissions can work. mkdir ~/bin; cp /usr/bin/gcc ~/bin; chmod 755 ~/bin/gcc . Then there must be a way to specify the compiler via an env var, like export CC=~/bin/gcc , Finally download a Perl source and compile it in your home-dir. Finally tell perlbrew that it has to manage that Perl too.
VPS cost is like 5 euros per month for 4 cpu cores (spec?), 8 GB ram, and most importantly unlimited traffic (but not bandwidth). That 5 euros buy you all the flexibility you will need. HOWEVER, I can't really tell what number of simultaneous visits that system can support.
| [reply]
[d/l]
[select] |
| [reply] |
cp: cannot open '/usr/bin/gcc' for reading: Permission denied
| [reply]
[d/l]
[select] |
