I haven’t managed a site on a shared host like godaddy in years, before I moved to Drupal 8 and I’m trying to shake the cobwebs loose and apply it to our composer managed world.
I’ve just been asked to port a site from a private server on linode to a Go Daddy shared server. On the current server, the site is currently managed by Composer and is using Drupal Scaffolding; web-root currently points to docroot in composer.json: so Drupal lives in public_html/docroot vendor and non-drupal files live in public_html. The site is working swimmingly on their current hosting. I prefer the practice of keeping vendor, private files, git and the like outside of Drupal so it can’t be directly accessed externally.
Correct me if I’m wrong, but I believe that for primary domains on GoDaddy docroot needs to be in public_html, so I’m trying to dope out how to best accomplish this. It seems to me that my options are to either change the scaffolding (update web-root in composer.json and rebuild the site with a composer install) or I could hack out some rewrite rules in .htaccess,
All that said some questions:
- Am I missing any other ways to accomplish this?
- Any pitfalls to either approach?
- Which would you recommend?
This client also does not want me using SSH going forward, so it looks like I’ll be building locally, deploying via FTP and using the interface to update config. It’ll be like 2015 again!
