Search the Community
Showing results for tags 'environment'.
I would like to have Prestashop on my local computer and online at the same level. Therefore I would like to download or upload the software. Is it possible to define Prestashop environments and different domains (e.g. prestashop.localhost and www.myliveprestashop.com) and database settings? With most solutions the environment is specified in the .htaccess file and the settings of the environment are loaded. There is config_dev.yml config_prod.yml under the folder app/config. Is that what these files are for? How can I solve the problem?
Hello, I have downloaded a live project of prestashop on my local environment. The live version is using SSL and because i don't want to create self-signed SSL Certificate I want to disable the SSL on my local environment. So what I did I changed the value of PS_SSL_ENABLED from myphpadmin from 1 to 0 but the site keeps redirecting me to https instead of the http. I checked the site urls but they are fine same as my htaccess. Does anyone have any idea what it keeps redirecting me to https? I'm using mac with chrome
Hi, I set up a test environment to check some problems I was facing without influencing the live site ( duplicated the site-folder and database and changed the settings.inc.php to point to new db) now when click on any product it goes alternatively from test to live environment, without evere going to product page anybody ever seen anything like this?
Hi, I would like to know if there is any official guide or guidelines to promote PrestaShop installations between environments. In case there are 2 or more environments for a shop (test environment, production environment), which are the recommended steps to take to promote from one environment to another? My concerns are: - promote the shop main configuration options - promote specific modules configuration options - promoting the catalog - promote changes in core or module files - avoid long downtimes To avoid some headaches, I'm thinking about this "simple solution": There would be 2 environments: test (private) and production (public). The test environment is where all the changes are made (with previous backups): core updates, module updates, shop configurations, catalog management, etc. Once the test environment is "accepted", it gets cloned to the production environment (with previous backup). The cloning procedure would have this steps: Backup production files Remove all the old files from production Copy all the files from test to production Backup production database Remove production database* Copy the database from test to production Change the /config/settings.inc.php with the production database values * I should save before the orders, the carts, the user information, etc before. Am I missing something? I just want to know if anyone has easier solutions, or solutions that minimize the downtime. How are you making your environment promotions?