# Update Process

##### Note: Before Update Take Backup of All Files And Database. Make .zip file and download all file, Go To phpmyadmin and select your database and export it.

Copy All files and paste to you folder replace file. Only be careful when replace files in public folder, don't copy .env file. Any user customize design and code please do not update. For database don not import all tables.

##### Update Version 1.3

1.2 Version Required then Copy All files of folder and paste to you folder and replace files, only be careful when replace files in public folder, don't copy`.env` file.Any user customize design and code please do not update.

After replacing the files successfully goto yourdomain.com/ota/update. If your domain contain public then goto yourdomain.com/public/ota/update. Read update pre-notes and FAQ properly, then check the agreement box and click on update. After the update completion you will be redirected to yourdomain with a successful update message.

But your images will not be visible on site for that: goto URL yourdomain.com/image/conversion. If your domain contain public then goto URL yourdomain.com/public/image/conversion. Again read instructions properly and make sure you have the backup and your system is up as it is a lengthy process. After reading the instructions carefully click on image conversion. It might take time accordingly the users products.

Once the process is complete you will see a successful message on your home page.

You successfully upgraded to version 1.3.

#### After update changes of 1.3

Some settings are changed in 1.3. To update the settings goto Settings > General Settings update the open exchange rate key (mandatory); if you enable the re-captcha than update re-captcha v2 keys.

Now you need to create cron job on your server.

#### For cpanel and shared hosting

Go to cpanel dashboard and find advanced and open cron job tab

After opening cron job you will see similar settings. For more information check below screenshot. Run the command

    php /path/to/artisan schedule:run 1>> /dev/null 2>&1
    or
    cd /path-to-your-project && php artisan schedule:run >> /dev/null 2>&1

After adding new cron job you will see similar output as in below screenshot.

For Check Cron Job is running or not after setup your cron job reload your site homepage and go to your project directory and open storage/logs and open file laravel.log. You will see a message like this

#### For ubuntu servers

To start the Laravel Scheduler itself, we only need to add one Cron job which executes every minute. Go to your terminal, ssh into your server, cd into your project and run this command.

    sudo crontab -e

This will open the server Cron tab file, paste the code below into the file, save and then exit. Make sure your replace path-to-your-project with your project directory ex. var/www/html/projectdirectory

    * * * * */usr/bin/php /var/www/project/artisan schedule:run >> /dev/null 2>&1

For Check Cron Job is running or not after setup your cron job reload your site homepage and go to your project directory and open storage/logs and open file laravel.log. You will see a message like this Check if Ubuntu cron working fine or by hitting this command
In Ubuntu, the cron service should start automatically. You can check it with these commands:

    sudo service cron status # checks if cron is running
    sudo service cron start  # starts it
    sudo service cron stop   # stops it

#### For localhost

For users who testing script on localhost like laragon, xammp, wammp or other tools
after run project go to project directory and open terminal/command prompt and hit command

    php artisan schedule:run

You will receive following similar output

##### Update Version 1.2

1.1 Version Required then Copy All files of folder and paste to you folder and replace files, only be careful when replace files in public folder, don't copy`.env` file.

##### Update Version 1.1

1.0 Version Required then Copy All files of folder and paste to you folder and replace files, only be careful when replace files in public folder, don't copy`.env` file.

Add these variable to .env file

    DEMO_LOCK=0