I am trying to deploy a Laravel app onto godaddy shared hosting. And have tried several solutions mentioned on this site and others, such as:
-Hosted Laravel 5.4 App shows "View [path.to.viewfile] not found."
-View [auth.login] not found at Shared Hosting Godaddy
However, my views still cannot be found, for some unknown reason that I cannot tell. I have tried the solutions mentioned here, but to no avail.
I checked the spelling of the views since Linux server is case sensitive.
the specific error can be viewed at : auctionSalvages.com
but in short::: View [simpleComponents.HeaderComponents.MainHeader] not found. (View: /home/hostname/AutoShop/resources/views/layouts/main.blade.php)
I have now successfully executed the following php artisan commands: clear-compiled,cache:clear,config:clear,route:clear and view:clear on the server through ssh.
but my view still returns above error..
any more ideas???
This may be a few years too late but here a few things you need to consider if this happened.
Make sure that all the files in the Public folder of your app is copied into the public_html folder of your godaddy hosting site. Make sure that the Settings in your cPanel File Manager (which is generally at the upper right corner) that Show Hidden Files (dotfiles) is checked.
Make sure the you have the .htaccess file in your public_html folder with the correct permissions.
Typically, when you transfer files into your hosting site, you do so by uploading a zip file and then extracting the zip file in the root directory of your site.
And then, when you copy the files from the Public folder of your app, you generally just Select All > Copy > Select public_html
However, sometimes, the files in your Public folder are hidden so you have to set the settings to Show Hidden File (dotfiles) to checked.
Related
Attempting to get LAMP working on my 32-bit Ubuntu 18.04 machine. I believe the set-up is close to correct. I have all Apache2, mysql, and PHP software installed. I have an index.php file located in folder /var/www/bookcorner directory which shows up as it should if I enter localhost/index.php in the browser address bar. This file may be edited in nano while saving the changes. However, I cannot use my editor Notepadqq (or presumably others) to edit the file.
Going through the file manager, I can select the file and open it in Notepadqq, but I cannot save it. I get the error, "folder does not exist". If I try a 'Save As' with Notepadqq, I do not see any folders past /var in the directory structure, though they obviously exist. The www folder and subfolders do not show up in Notepadqq.
There are three folders under /var/www which are
bookcorner
html
michaelsbookcorner.com
I have ownership of all of these folders
michaelsbookcorner.com is a live site at Infinityfree.net
I somehow got Apache2 to point to bookcorner for now which is fine. Eventually I would like to select between different websites but I only have one for now existing in another directory. I wish to begin utilizing LAMP rather than uploading PHP files to my hosting site all the time.
What settings/permissions/etc could I have missed here in order to get this working properly?
I am trying to configure the temporary directory on my Drupal install. Previously, I have been on a cPanel shared account, and all I would simply do is add '../tmp' to the settings and it all worked fine. I have recently outgrown my shared account and upgraded to a VPS, with CentOS and VestaCP. Now, when I enter '../tmp' it says that the folder 'does not exist and could not be created.' I have checked, and that folder is indeed there via file manager and FTP, is 755 permissioned etc. No matter what I try, it just doesn't seem to want to acknowledge it is there.
My CentOS and VestaCP installs have had VERY little tweaking, so they are pretty much default installs at the moment. I was advised to try a path such as:
/home/admin/web/MYDOMAIN/tmp
Other attempts have been:
/tmp and /home/admin/web/*/tmp
But they all threw up the same error. If I type just 'tmp', it works fine, but is then obviously within the web root directory, which is not ideal. Help?
In the end, it turned out that the best way is to use the pre setup and designated tmp folder for the whole install, which is located at /home/admin/tmp. This also allowed for uberCart credit card processing as well, which wasn't available via a normal ../cc either. The folder also allows for directories, so you could separate between domains and requirements, i.e.
/home/admin/tmp/domain.com or /home/admin/tmp/cc/domain.com
I have tried hosting my Laravel app in Godaddy. The homepage works well as well as the log ins and dashboard after logging in. But the other views return a InvalidArgumentException in FileViewFinder.php line 137: "View [path.to.viewfile] not found.
I'm returning the view from the controller with return view::make('path.to.viewfile')
It works well on my localhost using XAMPP. Does anybody know how to fix this?
Have you checked filenames and permission? file names are case sensitive in Linux (your hosting provider uses it)
You have to change directory permissions at your server. Directories and files within the storage and the bootstrap/cache directories should be writable (e.g. chmod 777)
I have tried running the following code, and even though it runs and sets the nginx blocks ok, its not linking to the folder in question with in the host machine.
serve projects.dev /home/vagrant/Code/projects.dev
When i then list the folders within the Code folder on the guest machine, i only get the folders that were created via the automated Yaml config file on init set up.
It seems not be creating the folder and/or linking to it at all with between the guest and host machines
Running it on a iMac OS Mavericks.
Vagrant 1.6.2
VirtualBox 4.3.12
That is strange. What I have is I have a folder mapped on the "folders" section from my host machine that inside contains all the sub-folders for all my projects in progress. So my nginx sites just basically link to the sub-folders inside this directory. If you have something like that it "should" show you the folders from your host inside that Code directory in your VM. Maybe post your YAML file to check it out?
My problem was the new Homestead file, use small c for spelling directory "code".
I was upgrading my homestead, so the old code folder was using capital c, spelled "Code".
I just change my Homeastead.yaml file from calling "code" to "Code".
So I'm new to Laravel 4, and I'm trying to figure out how to Symlink two parts of my site.
The first is apps/storage
The second is public/cache (this is where an image cache is stored)
I'd like to move both of these to a SSD on my server, however Laravel keeps throwing out an error whenever I try and setup these Symlinks.
That error is:
ErrorException
file_put_contents(/meta/services.json): failed to open stream: No such file or directory
Clearly it's unable to find the filesystem and the symlink isn't working with Laravel. But the symlink DOES work with individual files (such as a jpeg), so I'm positive there is no problem with the initial setup.
To clarify, the document root is set to httpdocs/public (via Plesk settings)
The apps (and framework) are located in the httpdocs folder which is no longer serving as the vhost root.
As I hinted at, it's a Plesk server. The owner belongs to the vhost, and the group belongs to psacln. But I don't think there are any permission/ownership problems, as I've verified the symlinks are working.
Looks like you have messed something else, because the path in the error message looks wrong to me:
file_put_contents(/meta/services.json)
IMO, it should be something like:
file_put_contents(/var/www/webapp/app/storage/meta/services.json)
Because, if you have done the symlink correctly you did something like
mv /var/www/webapp/app/storage /mnt/ssd/
ln -s /mnt/ssd/storage /var/www/webapp/app/storage
PHP is trying to write a file in the root /meta folder, where probably it doesn't have right.