public folder conflict in shared hosting

When stored the uploaded file, How you did that? Share your controller. I hope you did something like this.

'''

 $request->customer_photo->move(public_path('customer-photos'), $photoName);       

'''

Thanks senor for your response.

Ya, i follwed the similiar process,

this is my controller

if($request->hasFile('photo')){
            // check db & delete old photo first and empty the db value
            if(!empty($personals->photo)){
               if(file_exists(public_path().'/media/applicant_photo/'.$request->delete_photo)){
                    unlink(public_path().'/media/applicant_photo/'.$request->delete_photo);
                }
                $personals->photo = '';
            }
            // update new photo and save it
            $fileName = date('Y_m_d_h_i_s_') . $request->file('photo')->getClientOriginalName();
            $dirPath = public_path() . '/media/applicant_photo/';

            $request->file('photo')->move($dirPath, $fileName);
            $personals->photo = $fileName;
        }

the file should be stored in the

public_html/my_project/media/applicant_photo/flle_name.jpg,

but it goes to outer project folder that is created outside of the public_html

my_project/public/media/applicant_photo/file_name.jpg,

though there is no public folder in that directory, it is created automically when the storing process runs.

I am still searching and applying differenty but all goes failed.

The public_path seems to be hardcoded

/**
 * Get the path to the public / web directory.
 *
 * @return string
 */
public function publicPath()
{
    return $this->basePath.DIRECTORY_SEPARATOR.'public';
}

You could create your own function or override the path bound into the app container.

function public_html_path()
{
   return $this->basePath.DIRECTORY_SEPARATOR.'public_html';
}

Hello senor Snapy, I tried your suggested option and it worked too. But for some technical cause I had to keep all the folders in a single directory in public_html. I made some changes required on the basis of that directory setting and it worked fine. I added index files in all the sub-folders inside the public folder to stop directory access. It worked fine too. Everything is exactly set as I wanted. I just wanna ask you if there any problem that I created 2 index files (.html & .php) inside every sub-folder inside the public folder?

Thanks again senor.

you can prevent directory listing with htaccess or web server config. it's not necessary to create a file.

But, have you checked that someone cannot just open the .env file?

Thanks for your response senor Snapey, I checked the possible chance to access .env and it is secured I found. And I thought I should not write anything without learning what may be the after effect in .htaccess. ya, you are right. I think I can secure the directory through . htaccess.

Thank you again senor. I really like your suggestions.