Storage Link and Bassets in a shared hosting environment

[qontori]

I am a little confused over the implementation / need for the storage link in a shared hosting environment (Cpanel).

I have duplicated my questions here and at the bottom of this message for ease of reading.

Thanks in advance for your assistance ...

Questions

• It appears as though the basset configuration is not correct/not working at all. Please confirm
• Shouldn't the link be from username/public_html/mypublicfolder/ to username/myapp/storage so that public access to the assets are feasible without storing the assets publicly?
• It appears to me that the reason why the assets are loading during tests, is because there are two copies of the assets ie most under username/myapp/storage/app/public/basset and some under username/public_html/mypublicfolder/storage. Is this correct? Or is it because there is a copy of the username/public_html/mypublicfolder/storage/basset folder in username/myapp/storage/app/public/basset/public_html/storage/basset folder
• Is there any need for the username/myapp/public folder?

---

In version 4 I have the following Folder Structure and have been running my backpack / laravel app successfully. I do not use any form of symlink / storage linking and have just everything set at default. My Folder Structure is

Folder Structure v4 Cpanel shared hosting

- username/myapp
- username/myapp/public [assumed not in use for any reason]
- username/myapp/storage
- username/public_html/mypublicfolder
- username/public-html/mypublicfolder/css,js,index.php, etc.

inside my mypublicfolder/index.php, I configure to use the out of public_html location

- require __DIR__.'/../../myapp/vendor/autoload.php';
- $app = require_once __DIR__.'/../../myapp/bootstrap/app.php';

config files app, filesystems, all default

I am in the process of upgrading to version 6 [with the help of a freelancer] and things appear to be working correctly however I noticed some strange behavior, configurations and questioned some of their documentation before a live upgrade. Here is the V6 backpack/laravel folder structure noting one new folder username/public_html/mypublicfolder

Folder Structure v6

- username/myapp
- username/myapp/public [again I assume not in use]
- username/myapp/storage

- username/public_html/mypublicfolder
- username/public-html/mypublicfolder/css,js,index.php, etc.
- username/public_html/mypublicfolder/storage/basset

- inside username/public_html/mypublicfolder/storage/basset there are a few 

Storage Link

• I see there is a symlink, called "storage" - it looks like a folder with a link icon, located in username/myapp/public/
• When I click this link it takes me to username/myapp/storage/app/public [I know because I placed a temporary file there and clicked the link and it brings me to this folder
• Below username/myapp/storage/app/public there is a basset folder which contains many CDN, website, vendor/backpack and a copy of my username/public_html/storage/basset folder
• three is no link from username/public_html/mypublicfolder or any of the subfolders to the myapp folder outside of public_hml or anywhere for that matter

php artisan basset:check
I ran 'php artisan basset:check' from the username/myapp folder and received the following results

Initializing basset check ................................................................................................................... DONE
Checking cache storage ...................................................................................................................... DONE
Fetching a basset .......................................................................................................................... ERROR

ERROR Error fetching the file.

Backpack Basset failed to check it's working properly.
│
│ This may be due to multiple issues. Please ensure:
│ 1) APP_URL is correctly set in the .env file.
│ 2) Your server is running and accessible at https://username.mydomain.com/mypublicfolder
│ 3) The public disk is properly configured in config/filesystems.php.
│ Optionally, basset provides a disk named "basset", you can use it instead.
│ 4) The storage symlink exists and is valid (by default: public/storage).

APP_URL
APP_URL=https://username.mydoman.com
ASSET_URL=https://username.mydomain/mypublicfolder

filesystemsphp

• I have copied the code below but note that but the 'local' and 'public' sections do not have a "throw => false,"

    'disks' => [

        'local' => [
            'driver' => 'local',
            'root' => storage_path('app'),
        ],

        'public' => [
            'driver' => 'local',
            'root' => storage_path('app/public'),
            'url' => env('APP_URL').'/storage',
            'visibility' => 'public',
        ],

        's3' => [
            'driver' => 's3',
            'key' => env('AWS_ACCESS_KEY_ID'),
            'secret' => env('AWS_SECRET_ACCESS_KEY'),
            'region' => env('AWS_DEFAULT_REGION'),
            'bucket' => env('AWS_BUCKET'),
            'url' => env('AWS_URL'),
            'endpoint' => env('AWS_ENDPOINT'),
        ],

    ],

      'links' => [
        public_path('storage') => storage_path('app/public'),
    ],

Questions

• It appears as though the basset configuration is not correct/not working at all. Please confirm
• Shouldn't the link be from username/public_html/mypublicfolder/ to username/myapp/storage so that public access to the assets are feasible without storing the assets publicly?
• It appears to me that the reason why the assets are loading during tests, is because there are two copies of the assets ie most under username/myapp/storage/app/public/basset and some under username/public_html/mypublicfolder/storage. Is this correct? Or is it because there is a copy of the username/public_html/mypublicfolder/storage/basset folder in username/myapp/storage/app/public/basset/public_html/storage/basset folder
• Is there any need for the username/myapp/public folder?

Thanks again

[karandatwani92]

Hey @qontori

Generally, the storage and public folders are within your app folder:

• username/myapp/
  -- username/myapp/storage
  -- username/myapp/public

And the symlink is present inside username/myapp/public/ folder, named as public pointing {syslink-to-/storage/app/public}.

The problem, I can assume, is that you can't reconfigure the public dir path on shared cpanel hosting.

I found a tutorial that seems very similar to your implementation. This also includes creating a system link(step 6). I hope this will help.

You can also force Basset to use CDN links directly rather than caching files in storage. For this, you just need to add the following to your .env:

BASSET_DEV_MODE=true