Differences

This shows you the differences between two versions of the page.

--- merkalt:site_installation [2013/03/15 13:33] – dmitriy
+++ merkalt:site_installation [2017/09/11 15:21] (current) – old revision restored (2017/09/11 15:17) dmitriy
@@ Line 1: / Line 1: @@
 At first the test version should be setup into working state.
   - Creation of domain or new folder, setup of domain in control panel (if needed)
-  - setup default package with files (from svn - https://almeyda.repositoryhosting.com/svn/almeyda/trunk/merkalt). This should be done only for test site
+  - setup default package with files (from git -
-  - setup new instance VERY IMPORTANT - THIS WORK SHOULD BE DONE AT THE SAME TIME FOR LIVE AND TEST SITES! ALL configurationValues and InstanceGroupValues should be identical on test and live to keep them synchronized. Some of the queries below could be retrieved from admin queries.sql
+ssh://git@almeyda.repositoryhosting.com/almeyda/merkalt_sites.git). This should be done only for the test site (kupizamok.com or another).
-     - dsd
+**Important!** for subfolders based instances like merkalt.no/matmerker, merkalt.no/idband, merkalt.no/gratisnavnelapper THERE IS NO NEED to setup full package of files. Only special htaccess redirects to root instance, setup of instances/[instanceName] and necessary skins/ folders is needed. Required PHP files - [[merkalt::php_pages_short_review|Pages review]]
+  - setup new instance profile VERY IMPORTANT - THIS WORK SHOULD BE DONE AT THE SAME TIME FOR LIVE AND TEST SITES! ALL configurationValues and InstanceGroupValues should be identical on test and live to keep them synchronized. Some of the queries below could be retrieved from admin queries.sql (see [[merkalt::setupGlobalSql|Database pack for global changes setup]])
-  - edit Configurations settings for the instance. At first profile should be created (see [[merkalt::setup_sql|Database pack for setup]]), then Profile Groups could be edited in [[merkalt::config_settings|Configuration Settings]] editor. usually we need to edit such settings
+  - edit Configurations settings for the instance.  VERY IMPORTANT - THIS WORK SHOULD BE DONE AT THE SAME TIME FOR LIVE AND TEST SITES! Profile Groups could be edited in [[merkalt::config_settings|Configuration Settings]] editor. usually we need to edit such settings
     * General settings
     * Database connections settings
     * Checkout settings
-    * ...
+    * Affiliation tracking
-  - setup new individual database and [[merkalt::setup_sql|Database pack for setup]]. Payment methods settings are contained in DB, in //*_payment_methods//, //*_payment_methods_details// and //*_payment_methods_settings// tables.
+    * Mamut product indexes
-  - edit [[merkalt::configure_file|Configuration File]]. THis file is located are carried out to a single file //settings.inc.php//, placed in //config// subfolder in the instance root directory.
+  - setup new individual database (if needed) and also required tables - [[merkalt::setup_sql|Database pack for setup]]. Payment methods settings are contained in DB, in //*_payment_methods//, //*_payment_methods_details// and //*_payment_methods_settings// tables.
+  - edit [[merkalt::configure_file|Configuration File]]. Those settings are stored at a single file //settings.inc.php//, placed in //config// subfolder in the instance root directory.
-  - instance setup is stored in the //instances/[instanceName]// subfolder of root directory. it usually includes
+  - instance setup. Files are stored in the //instances/[instanceName]// subfolder of root directory. it usually includes
       - motifs folder
       - print_motifs folder
       - [[merkalt::xml_files|XML files]]
-  - edit [[merkalt::skins]]
+  - edit individual skin. [[merkalt::skins|Skins manual]]
+  - if rendering is enabled for the instance an output/ folder with 777 permissions should be created