flyflo Posted July 23, 2017 Report Posted July 23, 2017 Hallo, as I can see, you are using laravel, composer, artisan as a framework for the new phpvms. It is also possible to install and use the phpvms system on shared hosting product. I assume the most VAs are using shared hosting because of the more affordable price and with this product you will not get a ssh access to the server. It is possible to install all necessary php frameworks without ssh login? Florian Quote
t_bergman Posted July 23, 2017 Report Posted July 23, 2017 1 hour ago, flyflo said: Hallo, as I can see, you are using laravel, composer, artisan as a framework for the new phpvms. It is also possible to install and use the phpvms system on shared hosting product. I assume the most VAs are using shared hosting because of the more affordable price and with this product you will not get a ssh access to the server. It is possible to install all necessary php frameworks without ssh login? Florian Florian, I've got v4 working in its current state on shared hosting. Please be aware that v4 is still being developed and thus changes are likely, Nabeel (phpVMS's developer) has control over this and I know is working hard to make it easy for everyone to use. I do plan on releasing a short tutorial to get phpVMS v4 installed onto shared hosting however a requirement will be SSH access using a terminal such as PuTTY. Many shared hosting providers do provide SSH access (mine for example as a $2.50 one time fee). Quote
Moderators servetas Posted July 24, 2017 Moderators Report Posted July 24, 2017 As @t_bergman stated, phpVMS v4 can work on a shared hosting environment. It is not that difficult expecially if you are working on a linux environment and as soon as you provider provides you with SSH access. Some web hosting providers require justification, some others offer it for a specific cost, others offer it for a specific period of time in order to monitor it. You are going to need SSH during the installation of the phpVMS v4 and in case you want to update your software. Afterwards, SSH is not required (as far as I know). Also, for cpanel, Jailed Shell can be enough. Quote
flyflo Posted July 24, 2017 Author Report Posted July 24, 2017 (edited) Thank you for your answer. As you have noticed, shared hosting was not the correct description :-) I was thinking about hosting products without ssh access. btw, phpVMS4 is running inside a laraval box on my local machine, everything is fine. Edited July 24, 2017 by flyflo phpvms is running Quote
TAV1702 Posted August 31, 2017 Report Posted August 31, 2017 And if someone cant have SSH? I've been with the same host for working on 9 years now with virtually no down time ever. A move would suck real bad. Just saying. Quote
Administrators Nabeel Posted November 29, 2017 Administrators Report Posted November 29, 2017 The goal is going to be not requiring SSH. I'm going to have a packaged version that includes the /vendor directory already populated, so that should eliminate the need for running the composer install. In terms of needing to point to the phpvms/public directory... I've found that placing phpvms in the same directory as public_html, and then creating a subdomain (e.g, a www subdomain) and pointing it to the phpvms/public directory works. Then you can create a CNAME for the base domain to point to www. I think that should cover the install on a shared host. I'll be asking people to test this out in the alpha version. It is annoying, yes, but all modern frameworks are working this way now. The biggest advantage is security... especially with addons. With the code not being exposed, the chances for any attack are minimal. Luckily there haven't been any (except for a while ago due to a 3rd party library), but there are some that would definitely be vulnerable. If you have SSH access, you can create a symlink from public_html to phpvms/public, and then you don't need to worry about any CNAME stuff. One think I need to investigate is if you're able to do this from cPanel. Quote
web541 Posted November 29, 2017 Report Posted November 29, 2017 4 hours ago, Nabeel said: The goal is going to be not requiring SSH. I'm going to have a packaged version that includes the /vendor directory already populated, so that should eliminate the need for running the composer install. In terms of needing to point to the phpvms/public directory... I've found that placing phpvms in the same directory as public_html, and then creating a subdomain (e.g, a www subdomain) and pointing it to the phpvms/public directory works. Then you can create a CNAME for the base domain to point to www. I think that should cover the install on a shared host. I'll be asking people to test this out in the alpha version. It is annoying, yes, but all modern frameworks are working this way now. The biggest advantage is security... especially with addons. With the code not being exposed, the chances for any attack are minimal. Luckily there haven't been any (except for a while ago due to a 3rd party library), but there are some that would definitely be vulnerable. If you have SSH access, you can create a symlink from public_html to phpvms/public, and then you don't need to worry about any CNAME stuff. One think I need to investigate is if you're able to do this from cPanel. If you can't do it from cPanel, you could possibly do it from a PHP script (just looking at their manual) http://php.net/manual/en/function.symlink.php Quote
Administrators Nabeel Posted November 30, 2017 Administrators Report Posted November 30, 2017 7 hours ago, web541 said: If you can't do it from cPanel, you could possibly do it from a PHP script (just looking at their manual) http://php.net/manual/en/function.symlink.php Thanks, it's a bit roundabout, that will be something to explore for sure Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.