> For the complete documentation index, see [llms.txt](https://complainify.gitbook.io/complainify-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://complainify.gitbook.io/complainify-docs/getting-started/shared-hosting-installation.md).
# Shared hosting installation
This installation is completely manual
Hello, let's start the installation process by extracting the zip file you downloaded from Codecanyon to a folder.
First, let's start by creating a database on your cPanel or PleskPanel server (cPanel is recommended)
***
### Database install
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
***
### File upload
Now that the database is ready, we can proceed with editing the details and uploading the files.
.env file
You should update the database information in the `.env` file with the details of the database you created.
Additionally, you need to change the `APP_NAME` and `APP_URL` settings. For example, set the project name to 'Complainify' and the URL to ''.
Where is the .env file?
Go back to the folder you downloaded and check inside the 'upload\_file' folder.
.env file
After editing the file, we can re-zip all the files and upload them to our server.
Step 1
Step 2
Step 3
Step 4
***
### **Activating images after installation.**
If your server has terminal access, you can perform this operation with the command `php artisan storage:link`.\
If your server does not have terminal access, you need to create a symlink using the cron job command below. What does this do? It registers every image you upload in the storage folder, but this folder is not directly accessible from the outside, so you need to create a symlink. As a result, you need to run the cron job command every minute (\* \* \* \* \*) for it to work.
Please note that the `ln -s` command is a dangerous command, and improper use can lead to serious issues. Make sure you know the file paths on your hosting before running this.
example folder path
Once you find the path, just write the command by replacing the placeholders with the correct values. For example, in the following command, "home" refers to the main directory of your project, and "username" refers to the folder name in your path (e.g., "softbbsf"). "public\_html" refers to the root directory of your project, if it's at the root level, or it could be the folder name if it’s in a subdomain or different directory.
Here’s the final command structure:
* Replace **"home"** with your project's root directory (e.g., `/home`).
* Replace **"username"** with the folder name in your project path (e.g., `softbbsf`).
* Replace **"public\_html"** with the name of the folder where your project is located, like `public_html` or any other directory name if it is in a subdomain or custom folder.
After this, ensure that you copy the command exactly and replace the placeholders with the correct folder names.
|
