I
I
ildar-meyker2021-06-07 00:52:29
Laravel
ildar-meyker, 2021-06-07 00:52:29

It is necessary to simplify life on shared hosting when publishing laravel. How?

Now I have something like this folder structure:

site.ru
laravel-apps
...site-1.0.1
...site-1.0.2

That is, site.ru contains public content with edited index.php, and laravel-apps versions lie. Even in site.ru there is a symbolic link storage to the storage folder in the corresponding version.

Now the filling process is quite dreary for me.
1. I upload the new version and database
2. I transfer the current version to maintenance mode
3. I copy the storage of the current version to the new version
4. I update the site.ru, index.php resources and the symbolic link.
And everything works.

It would be nice to at least get rid of the stage of copying storage from one version to another. Is it possible to somehow take storage out of version limits, and make a symbolic link to it. Will it work? That is, will the application have problems with access when writing to the directory? I don't really know much about server administration and symbolic links.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
A
Alexander Medvedev, 2021-06-07
@lifestar

Is it possible to somehow move storage outside of versions, and make a symbolic link to it

Can
Will it work?

Will
That is, will the application have problems with access when writing to the directory?

Will not

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question