Move Laravel to another server error - php

I am trying to move a laravel project to a new server. Before moving on to the new server I am testing it on localhost.
I am getting the error like this: file_put_contents(/megashopping_dk_files/storage/framework/views/d2f79fe2bf4361439b4c43509087ad6167dfffd9.php): failed to open stream: No such file or directory
The original path in config.php was
0 => '/var/zpanel/hostdata/zadmin/public_html/megashopping_dk_files/resources/views',
which I have changed to
0 => '/megashopping_dk_files/resources/views',
I have already deleted all the files in the folders cache sessions and views in storage/framework
Again I have got two root folders with file structure like this:
1st root Folder - megashopping_dk
backend
compaign
css
fonts
img
js
library
....
2nd Root Folder - megashopping_dk_files
app
bootstrap
config
database
public
resources
storage
....
From the above what I understand is that the
contents of the First Root Folder should go in the root
and the contents of the second Root Folder should go alongwith the folder in contains.
Please advise me the right path?

TRY chmod -R guo+w storage
Few explanations
chmod -R guo+w storage : Whenever we add new service provider the cache folder for that service provider will be created in inside storage/framework . we need to make them writable from our application
php artisan optimize : to reuse all frequently used classes php will make an cached class in cache/service.php. So we if add new service we need to run it. We need to use it whenever we add new dependency without using composer.
php artisan cache:clear : clear all the above cache and remap everything
For more information read https://sentinelstand.com/article/laravel-5-optimization-commands

Remove the cached data. Go to storage\framework and remove all the files in sessions, cache and views
Once you are done with that, give proper permissions to your storage folder recursively.

Related

Issue with Storage on shared hosting

I am deploying my first project on a shared hosting.
I followed this tutorial to deploy the website and turn the public folder into the public_html folder of my hosting plan.
When I upload an image from my website (with storeAs() method), the file is uploaded in the private/storage folder, not the public one (where I would like).
The asset() function try to display the image from public_html/storage.
What can I do ?
Thank you :)
My files are like this :
private/
- app/
- bootstrap/
- config/
- database/
- resources/
- routes/
- storage/
- tests/
- vendor/
public_html/
- css/
- js/
- images/
- js/
- storage/
(Laravel 8, trying to be hosted on Hostinger)
The tutorial : https://dev.to/pushpak1300/deploying-laravel7-app-on-shared-hosting-hostinger-31cj
Why does this problem happen?
If you implement and need storage matter in your project then you need to link storage folder to the public folder for security reason and to make the URL simple, clean and readable by the users, so when you upload the laravel project to a server, you need to run the following command line to complete the linking process:
php artisan storage:link
and since you host the laravel project to a shared server, so you don’t have access to a terminal to run the above-mentioned command line . so I’ll show you a way to do that manually without using SSH or the terminal.
Steps to fix the problem
1- At localhost server-side (before uploading the project to the server), make sure that you have done filesystem configuration, then run the following command line:
php artisan storage:link
after that you will get a message “The links have been created.” and that is ok for now.
2- Upload the project to the server, the storage link will not work as you expected, so we need to start fixing this.
3- Go to the public folder you will find a folder called “storage”, delete it.
4- Go to routes folder and open “web.php” file, then copy & paste the following code at the top of the file:
Route::get('/linkstorage', function () {
Artisan::call('storage:link') // this will do the command line job
});
Don’t forget to save the changes.
Also, you can do the same process via “api.php” and using requests tools like postman.
5- Now we just need to run this code, so we need to do the GET request by entering the following URL at browser search bar:
“https://www.your-domain.com/public/index.php/linkstorage”
or
“https://www.your-domain.com/public/linkstorage”
this request will run the above code “Artisan::call('storage:link')” which is, in turn, will run the command line
PHP artisan storage: link
now you can go to the public folder and you will see the “storage” folder created again and marked as a shortcut folder and that means the public storage folder now is linked to the storage folder of the project.
6- Now if you upload or create a file to the storage folder, then it will appear in the public/storage folder too, now you can hit the URL of the file at the search bar of the browser and you will get the file successfully :).
Ok guys i found the solution !
Here is how to deploy your Laravel project on one shared hosting using public_html folder : https://dev.to/pushpak1300/deploying-laravel7-app-on-shared-hosting-hostinger-31cj
This will work but you can have a problem (like me) with the storeAs() method if you deal with file uploads.
To solve this problem, I edited the MyProject/config/filesystem.php by adding this in the available disks :
'public_folder' => [
'driver' => 'local',
'root' => 'PATH',
'url' => env('APP_URL').'/storage',
'visibility' => 'public',
]
Replace PATH with the complete path to your public storage (for example /home/you/domains/mydomain.com/public_html/storage/).
Now, open the controller which manage file upload and edit it like this :
request()->image->storeAs('/uploads', 'filename.png', 'public_folder');
This will upload the request()->image in public_html/storage/uploads/filename.png.
I hope it will help you if you had the same problem as me.

Storage in laravel says symlink - no such file

I deployed laravel app on shared hosting in public_html/app folder. Here is everything from public folder. In /../../files I have rest of files. When I do php artisan storage:link in files folder my console says
[ErrorException]
symlink(): No such file or directory
On localhost I upload files to storage/uploads folder. What to do now? I tried to change links but nothing works for me...
Go to /public directory and run:
rm storage
Go to Laravel root directory and run:
php artisan storage:link
Edited on May 1st 2018
This problem comes when laravel project is moved/copied to some other folder.
The storage link is still there thus causing the exception error. public/storage folder exists and points to wrong location and it needs to be deleted with rm storage command.
After that run php artisan storage:link in terminal and it will create the storage link.
This needs to be done EVERY time when laravel is moved/copied/deployed!
I'm face same error when use share hosting and my public directory move to public_html or different directory
like :
project directory in root name "project"
and public directory in root name "public_html"
when run artisan command by Artisan::call('storage:link'); then face this error.
Solution:
1st need to bind your public directory in app/Providers/AppServiceProvider register method
$this->app->bind('path.public', function() {
return base_path('../public_html');
});
Now run the command its working fine
Just in case your down here still without an answer.
I had trouble because I did the symlink locally, then copied the files to the server. In order to make it work I did the following:
$ cd path/to/laravel/root
// if public does not exist, first create it.
$ cd public
// if public/storage does not exist, first create it.
$ rm -r storage
$ cd ..
// Now it should work
$ php artisan storage:link
This usually happens after moving Laravel app to another directory
The actual storage directory is "/AppName/storage/app/public/"
Laravel creates a symbolic link pointing to actual storage dir "/AppName/public/storage"
Other meaning
"/AppName/public/storage" points to => "/AppName/storage/app/public/"
On changing root app directory to "/AnotherAppName/" symlink will still point to the old path
"/AnotherAppName/public/storage" => "/AppName/storage/app/public/"
my solution is to manually update the symlink using
ln -sfn /AnotherAppName/storage/app/public/ /AnotherAppName/public/storage
Anyone coming in the future using Laravel Forge. I had this error when I renamed my domain name in Forge.
The solution was to go into the public directory and delete the existing symlink which had been copied over from the original domain.
After this symlink had been deleted, I was able to run php artisan storage:link again and this worked correctly.
create new php file and put this code on the file:
<?php
symlink('/home/CpanelUser/storage/app/public', '/home/CpanelUserpublic_html/storage');
?>
"CpanelUser" change to youre cpanel user name or host name.
Upload this file to public_html folder (www) of site
execute file with write site name+this file in browser
done!
Example:
My file name is symlink.php and site name is www.anysite.com
upload symlink.php to public_html folder in host and get web address in browser
http://www.anysite.com/symlink.php
after execute this file storage folder creite in public folder in laravel and link to storage folder in app.
To fix this error on your server, change directory to the public and remove the symbolic link for the storage folder.
The following commands will help you remove the symbolic link from the public folder:
cd public
rm storage
After removing the symbolic link go back to the root folder using with the command below:
cd ..
Now create the symbolic link with the following command:
php artisan storage:link
After running the command successfully, you should get the following message
The [public/storage] directory has been linked.
I hope this post helps you.
SYMLINK(): No Such File or Directory Laravel
Follow these three steps:
Remove storage file from public folder.
rm public/storage
If storage folder is there in your root directory, remove public file inside app folder.
rm storage/app/public
Run link command
php artisan storage:link
Make sure the APP_URL configuration in .env file is set correctly. after that run following command line:
php artisan config:cache
php artisan storage:link
Go to config/filesystem.php in the symbolic links section in my case I removed public_path function and wrote my own path in it then run php artisan storage:link command again.
'links' => [
'/var/www/storage' => storage_path('app/public'),
],
Worked for me.
if issue is not fixed yet.
Do These Steps:
Delete storage link from public folder or run these commands.
a)
cd public
b) rm storage
Goto storage folder and check if app/public
folder exists otherwise create new folder.
Check if the error is fixed.
If these steps not fixed your issue delete storage folder and create new storage folder containing all necessary folders on it.
storage folder contains:
app, framework,logs
app contains: public
framework contains: cache, data,sessions,testing, views
Add this inside web.php and then hit this 'BASE_URL/linkstorage' URL once.
Now check the storage folder will be created inside the public folder. This will resolve your issue.
Route::get('/linkstorage', function () {
$targetFolder = base_path().'/storage/app/public';
$linkFolder = $_SERVER['DOCUMENT_ROOT'].'/storage';
symlink($targetFolder, $linkFolder);
});
My problem was that te symlink not was placed in /localhost/public/ but in /localhost/storage/app/
When i removed the symlink in /localhost/storage/app/ the artisan command works like a charm
In my code i placed this to prevent creating the wrong symlink
Route::get('/clear', function () {
Storage::deleteDirectory('public');
Storage::makeDirectory('public');
Artisan::call('route:clear');
Artisan::call('storage:link', [] );
});
If you are using shared hosting or you have deployed your project on a server with cPanel or DirectAdmin, you probably have a public_html instead of a public folder.
So one thing we usually do is change the Laravel public folder to public_html.
and then we go to our AppServiceProvider and bind the new path with the help of code below:
$this->app->bind('path.public', fn() => base_path('/public_html'));
But you should know the configuration files load before these register methods at your providers, so you have also to bind this before your kernel bootstrap your config files.
in order to do that, open index.php and write the code bellow after the $app variable defined:
$app->bind('path.public', fn() => base_path('/public_html'));
I know this might not seem a standard way, but It is working perfectly fine, and I haven't found any critical issue for it yet!
Add this to index.php
$app->bind('path.public', function() { return __DIR__; });
then on routes/web.php
add this
Route::get('/linkstorage', function () {
Artisan::call('storage:link');
});
Then run the link
I was using Vagrant and had the same problem. I removed to storage directory in public/storage but couldn't resolve the problem when using the command php artisan storage:link.
Therefore I connected with ssh to my vagrant box and ran the command there. It worked, so if you are running Vagrant and have the same problem this might help.
Delete the existing storage symbolic link (public/storage) and then run
php artisan storage:link command again.
In my case, I found that because I had moved all of the /public Laravel files to public_html (on my shared server), that the /public Laravel directory no longer existed.
After making a new "public" directory, I was able to successfully run the 'php artisan storage:link' command.
more instant i improve the answer of #suresh-pangeni
mv storage storage.bak // just for backup
mkdir -p storage/{app/public,framework/{cache,data,sessions,testing,views},logs}
php artisan storage:link
now its work
dont forget to
Go to /public directory and run:
then
rm storage before run on above command.
☺ pa storage:link
production 9999 ✗ The [public/storage] directory has been linked.
The solution is above but in separate parts, do one and two. Adding the route makes it easier for use case on external servers like shared hosts for example, thanks everyone
Go to config/filesystem.php in the symbolic links section in my case I removed public_path function and wrote my own path in it then run php artisan storage:link command again.
'links' => [
'/var/www/storage' => storage_path('app/public'),
],
For create storage link without terminal command(get at url)
Route::get('/linkstorage', function () {
$targetFolder = base_path().'/storage/app/public';
$linkFolder = $_SERVER['DOCUMENT_ROOT'].'/storage';
symlink($targetFolder, $linkFolder);
});
The issue normally happens when you changed the folder location after you generated your first symbolic link, I solved this isse by following the below steps:
Go in to the public folder and delete the storage folder(It will be labeled with red flag)
After deleting the storage folder, run php artisan storage:link and the issue will be solved
Follow these steps:
Step-1: server.php
<?php
/**
* Laravel - A PHP Framework For Web Artisans
*
* #package Laravel
* #author Taylor Otwell <taylor#laravel.com>
*/
$uri = urldecode(
parse_url($_SERVER['REQUEST_URI'], PHP_URL_PATH)
);
// This file allows us to emulate Apache's "mod_rewrite" functionality from the
// built-in PHP web server. This provides a convenient way to test a Laravel
// application without having installed a "real" web server software here.
if ($uri !== '/' && file_exists(__DIR__.'/public_html'.$uri)) {
return false;
}
require_once __DIR__.'/public_html/index.php';
Step-2: App\Providers\AppServiceProvider.php
/**
* Register any application services.
*
* #return void
*/
public function register()
{
//Public folder name changed with public_html
$this->app->bind('path.public', function(){
return base_path().'/public_html';
});
}
It is allow you to run the usual command php artisan serve
Step-3: config\filesystems.php
'links' => [
base_path('public_html/storage') => storage_path('app/public'),
],
To get the storage symbolic link properly with php artisan storage:link
Remember to change the path if is not public_html like for me
If someone faces the same error in Docker and Laravel9, try by deleting storage file in public folder and executing php artisan storage:link again. In my case it is 0KB.
In my case, I had added more than one symbolic link added to config/filesystems, one of the links is meant to be created in a subfolder but the parent folder doesn't exist ie the link leads to public/users/uploads but public/users folder does not exist.
So the first step was to create public/users folder before running php artisan storage:link
If you deleted public/storage file and has not fixed, yet. Try this composer dump-autoload.

Routes file not properly loaded

I have just installed a new installation of Laravel using composer as per the laravel docs. The documentation refers to the app/routes.php file which is used to map routes to controllers or closed functions. First, there was no app/routes.php file so I created one. Now the routes I've copied from the laravel documentation aren't being found when accessing via the browser. In fact the app/routes.php file isn't even being found by the application as I have put a die statement in there and nothing. It has nothing to do with .htaccess. I am using the default .htaccess and redirects are working. I thought maybe it has something to do with the composer.json autoload array so I have tested that and nothing. Not a jot. Either I'm being thick or there is something fundamental which isn't being explained in the docs. I'm running the latest version of laravel. Any ideas?
Laravel changed the folder structure with its latest release (which is version 5):
In 4.2: app/routes.php
In 5.0: app/Http/routes.php
There's also a few things you need to do in order for a Laravel Project to work. First (and this is the method I use) create a symbolic link to your project's public folder:
ln -s /path/to/webroot/example_app/public /path/to/webroot/example
Next, change the permissions on your storage folder:
chmod 777 -R storage
You should now be able to access localhost/example and the Laravel 5 welcome page should show up. Usually I call my project example_app and create a link to a folder called example, so I can easily access it via localhost/example
In Laravel 5, the routes file is located elsewhere: app/Http/routes.php.
Basically I did chmod 777 on the storage and vendor files and it started working

Copying Assets to Web root folder instead of Web/Bundles

I have Symfony project in which i want to copy images to web folder. So I used bellow command.
php app/console assets:install web
It copy all images to Web/bundles/framework. I want all images in Web root folder.
Please suggest me how can i change the path to store all images or assets to root folder of web instead of storing in bundles.
You cannot do that, because the default bundles/ directory is hardcoded in the source code:
Symfony\Bundle\FrameworkBundle\Command\AssetsInstallCommand - Line 83
$bundlesDir = $targetArg.'/bundles/';
So I suggest either sticking to that convention or submitting a PR to the Symfony core repository to parametrize this directory.

Need advice/help with website structure with caching, don't want to set 777 to doc root

I have a web application, based on CodeIgniter framework, which simply fetches data from stock exchange feeds and displays it. To enable caching the plan is to create a static HTML file once the stock exchange is closed coz there will not be any change in the stocks. Here is the structure for doc root of website
/index.php the CI controller
/application
/system
The URLs are
mysite.com/marketwatch.html - served by index method of marketwatch controller
mysite.com/marketwatch/marketindex/some-index-name.html - served by marketindex method of marketwatch controller and takes some-index-name as argument
mysite.com/marketwatch/scripdetails/some-scrip-name.html - served by scripdetails method of marketwatch controller and takes some-scrip-name as argument
Now what I can do is to create a path like DOCROOT/marketwatch/marketindex and DOCROOT/marketwatch/scripdetails/ and set 777 perms on these two so that at right time of the day the files are created in these two folders and .htaccess will direct Apache to serve these files instead of invoking whole CI framework and save sever of some botheration. The problem is
setting 777 for a folder that is served by webserver sounds wrong
I can't set 777 perms for doc root to create marketwatch.html
Can some one guide me how to solve this issue?
If you create the "cached" files in advance (even if they are empty) and give them 0666 permissions, PHP will be allowed to modify these files to update them (but don't never delete them, or they'll lose those permissions and they won't be the same the next time you create them).
You can try to set 0777 permissions with chmod function from php.

Categories