How to upload a project to a simple hosting without ssh?

Question

Software Deployment

Laravel version 5.7. Files uploaded via FTP,
db-mysql, sql database transferred to hosting.
Error 500
env in browser

spoiler

APP_NAME=Laravel
APP_ENV=local
APP_KEY=base64:key
APP_DEBUG=false
APP_URL=https://site.hhos.ru

LOG_CHANNEL=stack

DB_CONNECTION=mysql
DB_HOST=localhost
DB_PORT=3306
DB_DATABASE=login_dbname
DB_USERNAME=mysql
DB_PASSWORD=mysql

BROADCAST_DRIVER=log
CACHE_DRIVER=file
QUEUE_CONNECTION=sync
SESSION_DRIVER=file
SESSION_LIFETIME=120

REDIS_HOST=127.0.0.1
REDIS_PASSWORD=null
REDIS_PORT=6379

MAIL_DRIVER=smtp
MAIL_HOST=smtp.mailtrap.io
MAIL_PORT=2525
MAIL_USERNAME=null
MAIL_PASSWORD=null
MAIL_ENCRYPTION=null

PUSHER_APP_ID=
PUSHER_APP_KEY=
PUSHER_APP_SECRET=
PUSHER_APP_CLUSTER=mt1

MIX_PUSHER_APP_KEY="${PUSHER_APP_KEY}"
MIX_PUSHER_APP_CLUSTER="${PUSHER_APP_CLUSTER}"

THEME=white

.htaccess (1 option) at the root

spoiler

rm -rf public_html
ln -s public public_html

Option 2

spoiler

<IfModule mod_rewrite.c>
    RewriteEngine On

    RewriteRule ^(.*)$ public/$1 [L]
</IfModule>

database.php (/domains/site.hhos.ru/public_html/config)

spoiler

'mysql' => [
            'driver' => 'mysql',
            'host' => env('DB_HOST', '127.0.0.1'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'unix_socket' => env('DB_SOCKET', ''),
            'charset' => 'utf8mb4',
            'collation' => 'utf8mb4_unicode_ci',
            'prefix' => '',
            'prefix_indexes' => true,
            'strict' => true,
            'engine' => null,
        ],

Answer 1

The first is reading and access.
The second is encoding.
The most common cause of error 500 (Internal Server Error, internal server error) is the incorrect syntax of the .htaccess file or the presence of unsupported directives in it. Most often, it is enough to comment out the Options directive (to do this, put a hash mark at the beginning of the line - #), and the problem will disappear.
Error 500 can also be caused by mishandling CGI scripts:
CGI scripts must have UNIX (\n) line endings, not Windows (\r\n) line endings. To do this, they must be uploaded to the server via FTP in ASCII mode.
CGI scripts and folders in which they are located must be writable only by the owner, that is, they must have the rights 0755 (drwxr-xr-x).
As a result of the CGI script, incorrect HTTP response headers were generated. In this case, to solve the problem, it is useful to refer to the error_log (it can be found in the control panel in the "Hosting / Statistics / Log files / Errors" section).