Recommend a good HOW-TO about proper LAMP/Debian setup

Question

linux

There are a lot of manuals on the Internet, but as a rule, half of them simply duplicate each other and contradict each other.

In general, what is needed:

Apache + nginx + MySQL + well, in general, the entire standard set is already there.

He needs to configure SVN in such a way that the commit from Tortoise SVN gets immediately into the document_root of the input with the right permissions, so as not to set the permissions every time in a new way.

So that you can correctly set the rights in proftpd in such a way that after each file upload via FTP you do not have to rewrite the rights to the directories using chmod, because otherwise PHP cannot write anything to these directories.

I wrote a little chaotically, sorry if that.

Thank you.

Answer 1

Manuals on the Internet duplicate each other - I saw it, but there are no direct contradictions.
Try library.linode.com for example.

Answer 2

You will not find a single manual for such a “I want” mountain, but in principle there is nothing non-trivial here.
I can only offer my help - in the profile you can find all my IM contacts.

Answer 3

opennet.ru

Answer 4

www.ewanleith.com/blog/900/10-million-hits-a-day-with-wordpress-using-a-15-server

Answer 5

As for installing software, in Debian this is done with sudo apt-get install, but reading the manual on apt-get and generally on packages in Debian would be useful. About setting up mysql (the /etc/my.ini file) is written somewhere on the official MySQL website in the manual. About setting up Apache (/etc/apache2) is also written on his website.
Reading fragmentary "manuals" from the Internet, where nothing is explained properly, but simply suggested to copy commands, is harmful: they may not be suitable for your version of the OS or software, or something else, cause errors, contain vulnerabilities.
> He needs to configure SVN in such a way that the commit from Tortoise SVN gets immediately into the document_root of the input with the right permissions, so as not to set permissions every time in a new way.
This is the wrong approach. The correct approach is called deployment and is done for small projects with a bash script written on the knee (which, for example, creates a folder, makes svn export into it, and then copies the files over the old ones in the web directory), for large ones - with specialized utilities.
Plus, it's unwise to publish committed code directly from the repository without testing.
As for the rights to proftpd (vsftpd seems to be safer and better, isn't it?), this is achieved, firstly, by adding the uploader user and the web server to the same group (which has access to the web folder), and secondly, by setting options in the FTP server config, with what rights to create files and folders.
I personally have not seen a normal/adequate/understandable manual anywhere for everything listed, so all that remains is to read the original manuals for the products.