How to configure an existing Magento 2.1.7 project in another PC and Database?How to setup magento 2.1 from existing projectMagento 2 Version Update Dilemma (Cloned from Git Repo)Magento > 2.1.7 admin 404 (2.1.8 and 2.1.9)Magento 2 failed database rollback cannot add foreign key constraintsClone Magento 2 respository from git causing installing new project not loading existingMagento 2 InvalidArgumentException Could not find a matching version of packageUpgrading Magento 2.1.7 to 2.1.14Magento 2 How to added languages packs to git repo?magento 2 lost code for EAV attributesThe table Customer_grid_flat is deleted magento 2

Can a level 2 Warlock take one level in rogue, then continue advancing as a warlock?

Negative Resistance

Work requires me to come in early to start computer but wont let me clock in to get paid for it

How can I practically buy stocks?

How to not starve gigantic beasts

Can a stored procedure reference the database in which it is stored?

Apply a different color ramp to subset of categorized symbols in QGIS?

What was Apollo 13's "Little Jolt" after MECO?

A ​Note ​on ​N!

All ASCII characters with a given bit count

What is the unit of time_lock_delta in LND?

Combinatorics problem, right solution?

Von Neumann Extractor - Which bit is retained?

A strange hotel

Find a stone which is not the lightest one

How bug prioritization works in agile projects vs non agile

Is Electric Central Heating worth it if using Solar Panels?

How much cash can I safely carry into the USA and avoid civil forfeiture?

std::unique_ptr of base class holding reference of derived class does not show warning in gcc compiler while naked pointer shows it. Why?

How can I get rid of an unhelpful parallel branch when unpivoting a single row?

How can I wire a 9-position switch so that each position turns on one more LED than the one before?

Would the change in enthalpy (ΔH) for the dissolution of urea in water be positive or negative?

How long after the last departure shall the airport stay open for an emergency return?

My bank got bought out, am I now going to have to start filing tax returns in a different state?



How to configure an existing Magento 2.1.7 project in another PC and Database?


How to setup magento 2.1 from existing projectMagento 2 Version Update Dilemma (Cloned from Git Repo)Magento > 2.1.7 admin 404 (2.1.8 and 2.1.9)Magento 2 failed database rollback cannot add foreign key constraintsClone Magento 2 respository from git causing installing new project not loading existingMagento 2 InvalidArgumentException Could not find a matching version of packageUpgrading Magento 2.1.7 to 2.1.14Magento 2 How to added languages packs to git repo?magento 2 lost code for EAV attributesThe table Customer_grid_flat is deleted magento 2






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















I am new to Magento.
I have a working Magento 2.1.7 project and want to put it in a git repository.



If I put the working Magento directory into git and clone the repository to a local machine how do I install the existing project and do the database configuration?



I tried copy pasting the existing repository to another machine and tried to install it by following the normal procedure but it didn't work, instead I got this error:



An error has happened during application run. See exception log for details. 


I also tried to import the database as well but I got this error while importing:



Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in <b>Unknown</b> on line <b>0</b><br /> SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO" 


I extended the max_input_vars to 10000 in the php.ini file but still, I get the same error.



Please suggest me about how can I configure and install an existing Magento 2.1.7 project ** because I want to put the working project to GIT for my team to work with !**.










share|improve this question
















bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Could you update your question with the errors you get in the exception log?

    – diazwatson
    Aug 16 '17 at 10:48

















0















I am new to Magento.
I have a working Magento 2.1.7 project and want to put it in a git repository.



If I put the working Magento directory into git and clone the repository to a local machine how do I install the existing project and do the database configuration?



I tried copy pasting the existing repository to another machine and tried to install it by following the normal procedure but it didn't work, instead I got this error:



An error has happened during application run. See exception log for details. 


I also tried to import the database as well but I got this error while importing:



Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in <b>Unknown</b> on line <b>0</b><br /> SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO" 


I extended the max_input_vars to 10000 in the php.ini file but still, I get the same error.



Please suggest me about how can I configure and install an existing Magento 2.1.7 project ** because I want to put the working project to GIT for my team to work with !**.










share|improve this question
















bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Could you update your question with the errors you get in the exception log?

    – diazwatson
    Aug 16 '17 at 10:48













0












0








0


1






I am new to Magento.
I have a working Magento 2.1.7 project and want to put it in a git repository.



If I put the working Magento directory into git and clone the repository to a local machine how do I install the existing project and do the database configuration?



I tried copy pasting the existing repository to another machine and tried to install it by following the normal procedure but it didn't work, instead I got this error:



An error has happened during application run. See exception log for details. 


I also tried to import the database as well but I got this error while importing:



Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in <b>Unknown</b> on line <b>0</b><br /> SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO" 


I extended the max_input_vars to 10000 in the php.ini file but still, I get the same error.



Please suggest me about how can I configure and install an existing Magento 2.1.7 project ** because I want to put the working project to GIT for my team to work with !**.










share|improve this question
















I am new to Magento.
I have a working Magento 2.1.7 project and want to put it in a git repository.



If I put the working Magento directory into git and clone the repository to a local machine how do I install the existing project and do the database configuration?



I tried copy pasting the existing repository to another machine and tried to install it by following the normal procedure but it didn't work, instead I got this error:



An error has happened during application run. See exception log for details. 


I also tried to import the database as well but I got this error while importing:



Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in <b>Unknown</b> on line <b>0</b><br /> SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO" 


I extended the max_input_vars to 10000 in the php.ini file but still, I get the same error.



Please suggest me about how can I configure and install an existing Magento 2.1.7 project ** because I want to put the working project to GIT for my team to work with !**.







magento2 magento-2.1 magento-2.1.7






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 16 '17 at 11:11









diazwatson

1,59411425




1,59411425










asked Aug 16 '17 at 8:02









kaushik kumar roykaushik kumar roy

329




329





bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.














  • Could you update your question with the errors you get in the exception log?

    – diazwatson
    Aug 16 '17 at 10:48

















  • Could you update your question with the errors you get in the exception log?

    – diazwatson
    Aug 16 '17 at 10:48
















Could you update your question with the errors you get in the exception log?

– diazwatson
Aug 16 '17 at 10:48





Could you update your question with the errors you get in the exception log?

– diazwatson
Aug 16 '17 at 10:48










2 Answers
2






active

oldest

votes


















0














Change folllowing in php.ini and restart server.
memory_limit to 1G
post_max_size = 50M
upload_max_filesize = 50M
and also change max_execution_time to maximum time like 100 etc.



Also assign permissions to var and pub folders for this error
An error has happened during application run. See exception log for details.






share|improve this answer






























    0














    First of all, make sure that you have set the proper settings in php.ini configuration file. To see the recommended settings, please check this out:



    http://devdocs.magento.com/guides/v2.0/install-gde/trouble/php/tshoot_php-set.html



    Now make sure you have installed composer and other required PHP extensions (install missing PHP extensions). You can check out the system requirements for Magento 2 here:



    http://devdocs.magento.com/guides/v2.0/install-gde/system-requirements-tech.html



    Next, check out your files and folder permissions. Magento uses a three-bit mask that you subtract from the UNIX defaults of 666 for files and 777 for directories. Here’s what that means:



    • 775 for directories, which means full control by the user, complete
      control by the group, and enables everyone to traverse the directory.
      Shared hosting providers typically require these permissions.


    • 664 for files, which means writable by the user, writable by the
      group, and read-only for everyone else.


    After making sure of all the above things, migrate your Magento 2 store from one location to another with the following steps:



    1. Export Magento 2 Database



    By default, you may have PHPMyAdmin or a similar tool that is capable of exporting your database. Open your database tool and export your Magento 2 database in the .sql file format, because most of the database tools support the .sql file.



    2. Backup and Transfer Magento 2 Files & Folders



    After exporting your database, now you will need to download all files & folders of Magento 2 from your current location and upload them to the new location. It might be a time-consuming task, as it depends on how big your Magento 2 store is. If possible, a good approach is to create a zip archive of the files & folders before downloading them.



    Go to Magento 2 installation directory, create a zip archive of all the files & folders and then download it.



    Upload the downloaded zip file to the new location and extract it to the new desired destination folder for the Magento 2.



    3. Import Magento 2 Database



    Once you have transferred the Magento 2 files & folders, you should import the database to the new server. Go to the PHPMyAdmin, create a new database. Assign credentials to the database or create new username and password for it. In step 1, as we had already exported the database, import the database .sql file into this new database.



    4. Edit Magento 2 Configurations



    We are done with exchanging files between both the locations. Now it’s the time to configure your Magento 2 store with your new location. First, you need to edit the app/etc/env.php file with new Magento 2 database configurations according to your new server. Open the env.php file and alter the lines below:



     ‘db’ =>

    array (

    ‘table_prefix’ => ”,

    ‘connection’ =>

    array (

    ‘default’ =>

    array (

    ‘host’ => ‘DATABASE_HOST’,

    ‘dbname’ => ‘DATABASE_NAME’,

    ‘username’ => ‘DATABASE_USERNAME’,

    ‘password’ => ‘DATABASE_PASSWORD’,

    ‘active’ => ‘1’,

    ),

    ),

    ),


    Where:



    ‘host’ is the database hostname. Most commonly used host is “localhost”.



    ‘dbname’ is the database name. Use the one you had created in step 3.



    ‘username’ is a username that has full privileges to your new database.



    ‘password’ is the password for that particular database user.



    New server means new domain name. You have to replace old server domain name with new domain name. For this, you need to modify the value of web/unsecure/base_url and web/secure/base_url in core_config_data table. Enter the new domain name in the value column for both records.



    5. Clear Magento 2 Cache, Sessions and Deploy Static Content



    The final step is to clear the Magento 2 cache and deploy static content. Go to following paths and delete everything:



    ROOT > var > cache > *DELETE ALL*
    ROOT > var > page_cache > *DELETE ALL*
    ROOT > var > session > *DELETE ALL*
    ROOT > pub > static > DELETE ALL EXCEPT .HTACCESS


    Now, we are setting up static content to deploy on our Magento 2 store. To perform this task, using Command Prompt, navigate to the installation directory of Magento 2 and run the following Magento 2 CLI Command:



    php bin/magento setup:static-content:deploy




    If you get any error, check your PHP.EXE and PHP.INI Environment
    Variable




    Next, flush Magento cache by running php bin/magento cache:flush in CMD.



    And finally, to Reindex Magento Static Blocks run php bin/magento indexer:reindex command.



    You are done with successful migration of Magento 2 store. If you face any issue, do not hesitate to comment!






    share|improve this answer























      Your Answer








      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "479"
      ;
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function()
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled)
      StackExchange.using("snippets", function()
      createEditor();
      );

      else
      createEditor();

      );

      function createEditor()
      StackExchange.prepareEditor(
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader:
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      ,
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );













      draft saved

      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f189259%2fhow-to-configure-an-existing-magento-2-1-7-project-in-another-pc-and-database%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      Change folllowing in php.ini and restart server.
      memory_limit to 1G
      post_max_size = 50M
      upload_max_filesize = 50M
      and also change max_execution_time to maximum time like 100 etc.



      Also assign permissions to var and pub folders for this error
      An error has happened during application run. See exception log for details.






      share|improve this answer



























        0














        Change folllowing in php.ini and restart server.
        memory_limit to 1G
        post_max_size = 50M
        upload_max_filesize = 50M
        and also change max_execution_time to maximum time like 100 etc.



        Also assign permissions to var and pub folders for this error
        An error has happened during application run. See exception log for details.






        share|improve this answer

























          0












          0








          0







          Change folllowing in php.ini and restart server.
          memory_limit to 1G
          post_max_size = 50M
          upload_max_filesize = 50M
          and also change max_execution_time to maximum time like 100 etc.



          Also assign permissions to var and pub folders for this error
          An error has happened during application run. See exception log for details.






          share|improve this answer













          Change folllowing in php.ini and restart server.
          memory_limit to 1G
          post_max_size = 50M
          upload_max_filesize = 50M
          and also change max_execution_time to maximum time like 100 etc.



          Also assign permissions to var and pub folders for this error
          An error has happened during application run. See exception log for details.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 16 '17 at 10:19









          Ashar RiazAshar Riaz

          508519




          508519























              0














              First of all, make sure that you have set the proper settings in php.ini configuration file. To see the recommended settings, please check this out:



              http://devdocs.magento.com/guides/v2.0/install-gde/trouble/php/tshoot_php-set.html



              Now make sure you have installed composer and other required PHP extensions (install missing PHP extensions). You can check out the system requirements for Magento 2 here:



              http://devdocs.magento.com/guides/v2.0/install-gde/system-requirements-tech.html



              Next, check out your files and folder permissions. Magento uses a three-bit mask that you subtract from the UNIX defaults of 666 for files and 777 for directories. Here’s what that means:



              • 775 for directories, which means full control by the user, complete
                control by the group, and enables everyone to traverse the directory.
                Shared hosting providers typically require these permissions.


              • 664 for files, which means writable by the user, writable by the
                group, and read-only for everyone else.


              After making sure of all the above things, migrate your Magento 2 store from one location to another with the following steps:



              1. Export Magento 2 Database



              By default, you may have PHPMyAdmin or a similar tool that is capable of exporting your database. Open your database tool and export your Magento 2 database in the .sql file format, because most of the database tools support the .sql file.



              2. Backup and Transfer Magento 2 Files & Folders



              After exporting your database, now you will need to download all files & folders of Magento 2 from your current location and upload them to the new location. It might be a time-consuming task, as it depends on how big your Magento 2 store is. If possible, a good approach is to create a zip archive of the files & folders before downloading them.



              Go to Magento 2 installation directory, create a zip archive of all the files & folders and then download it.



              Upload the downloaded zip file to the new location and extract it to the new desired destination folder for the Magento 2.



              3. Import Magento 2 Database



              Once you have transferred the Magento 2 files & folders, you should import the database to the new server. Go to the PHPMyAdmin, create a new database. Assign credentials to the database or create new username and password for it. In step 1, as we had already exported the database, import the database .sql file into this new database.



              4. Edit Magento 2 Configurations



              We are done with exchanging files between both the locations. Now it’s the time to configure your Magento 2 store with your new location. First, you need to edit the app/etc/env.php file with new Magento 2 database configurations according to your new server. Open the env.php file and alter the lines below:



               ‘db’ =>

              array (

              ‘table_prefix’ => ”,

              ‘connection’ =>

              array (

              ‘default’ =>

              array (

              ‘host’ => ‘DATABASE_HOST’,

              ‘dbname’ => ‘DATABASE_NAME’,

              ‘username’ => ‘DATABASE_USERNAME’,

              ‘password’ => ‘DATABASE_PASSWORD’,

              ‘active’ => ‘1’,

              ),

              ),

              ),


              Where:



              ‘host’ is the database hostname. Most commonly used host is “localhost”.



              ‘dbname’ is the database name. Use the one you had created in step 3.



              ‘username’ is a username that has full privileges to your new database.



              ‘password’ is the password for that particular database user.



              New server means new domain name. You have to replace old server domain name with new domain name. For this, you need to modify the value of web/unsecure/base_url and web/secure/base_url in core_config_data table. Enter the new domain name in the value column for both records.



              5. Clear Magento 2 Cache, Sessions and Deploy Static Content



              The final step is to clear the Magento 2 cache and deploy static content. Go to following paths and delete everything:



              ROOT > var > cache > *DELETE ALL*
              ROOT > var > page_cache > *DELETE ALL*
              ROOT > var > session > *DELETE ALL*
              ROOT > pub > static > DELETE ALL EXCEPT .HTACCESS


              Now, we are setting up static content to deploy on our Magento 2 store. To perform this task, using Command Prompt, navigate to the installation directory of Magento 2 and run the following Magento 2 CLI Command:



              php bin/magento setup:static-content:deploy




              If you get any error, check your PHP.EXE and PHP.INI Environment
              Variable




              Next, flush Magento cache by running php bin/magento cache:flush in CMD.



              And finally, to Reindex Magento Static Blocks run php bin/magento indexer:reindex command.



              You are done with successful migration of Magento 2 store. If you face any issue, do not hesitate to comment!






              share|improve this answer



























                0














                First of all, make sure that you have set the proper settings in php.ini configuration file. To see the recommended settings, please check this out:



                http://devdocs.magento.com/guides/v2.0/install-gde/trouble/php/tshoot_php-set.html



                Now make sure you have installed composer and other required PHP extensions (install missing PHP extensions). You can check out the system requirements for Magento 2 here:



                http://devdocs.magento.com/guides/v2.0/install-gde/system-requirements-tech.html



                Next, check out your files and folder permissions. Magento uses a three-bit mask that you subtract from the UNIX defaults of 666 for files and 777 for directories. Here’s what that means:



                • 775 for directories, which means full control by the user, complete
                  control by the group, and enables everyone to traverse the directory.
                  Shared hosting providers typically require these permissions.


                • 664 for files, which means writable by the user, writable by the
                  group, and read-only for everyone else.


                After making sure of all the above things, migrate your Magento 2 store from one location to another with the following steps:



                1. Export Magento 2 Database



                By default, you may have PHPMyAdmin or a similar tool that is capable of exporting your database. Open your database tool and export your Magento 2 database in the .sql file format, because most of the database tools support the .sql file.



                2. Backup and Transfer Magento 2 Files & Folders



                After exporting your database, now you will need to download all files & folders of Magento 2 from your current location and upload them to the new location. It might be a time-consuming task, as it depends on how big your Magento 2 store is. If possible, a good approach is to create a zip archive of the files & folders before downloading them.



                Go to Magento 2 installation directory, create a zip archive of all the files & folders and then download it.



                Upload the downloaded zip file to the new location and extract it to the new desired destination folder for the Magento 2.



                3. Import Magento 2 Database



                Once you have transferred the Magento 2 files & folders, you should import the database to the new server. Go to the PHPMyAdmin, create a new database. Assign credentials to the database or create new username and password for it. In step 1, as we had already exported the database, import the database .sql file into this new database.



                4. Edit Magento 2 Configurations



                We are done with exchanging files between both the locations. Now it’s the time to configure your Magento 2 store with your new location. First, you need to edit the app/etc/env.php file with new Magento 2 database configurations according to your new server. Open the env.php file and alter the lines below:



                 ‘db’ =>

                array (

                ‘table_prefix’ => ”,

                ‘connection’ =>

                array (

                ‘default’ =>

                array (

                ‘host’ => ‘DATABASE_HOST’,

                ‘dbname’ => ‘DATABASE_NAME’,

                ‘username’ => ‘DATABASE_USERNAME’,

                ‘password’ => ‘DATABASE_PASSWORD’,

                ‘active’ => ‘1’,

                ),

                ),

                ),


                Where:



                ‘host’ is the database hostname. Most commonly used host is “localhost”.



                ‘dbname’ is the database name. Use the one you had created in step 3.



                ‘username’ is a username that has full privileges to your new database.



                ‘password’ is the password for that particular database user.



                New server means new domain name. You have to replace old server domain name with new domain name. For this, you need to modify the value of web/unsecure/base_url and web/secure/base_url in core_config_data table. Enter the new domain name in the value column for both records.



                5. Clear Magento 2 Cache, Sessions and Deploy Static Content



                The final step is to clear the Magento 2 cache and deploy static content. Go to following paths and delete everything:



                ROOT > var > cache > *DELETE ALL*
                ROOT > var > page_cache > *DELETE ALL*
                ROOT > var > session > *DELETE ALL*
                ROOT > pub > static > DELETE ALL EXCEPT .HTACCESS


                Now, we are setting up static content to deploy on our Magento 2 store. To perform this task, using Command Prompt, navigate to the installation directory of Magento 2 and run the following Magento 2 CLI Command:



                php bin/magento setup:static-content:deploy




                If you get any error, check your PHP.EXE and PHP.INI Environment
                Variable




                Next, flush Magento cache by running php bin/magento cache:flush in CMD.



                And finally, to Reindex Magento Static Blocks run php bin/magento indexer:reindex command.



                You are done with successful migration of Magento 2 store. If you face any issue, do not hesitate to comment!






                share|improve this answer

























                  0












                  0








                  0







                  First of all, make sure that you have set the proper settings in php.ini configuration file. To see the recommended settings, please check this out:



                  http://devdocs.magento.com/guides/v2.0/install-gde/trouble/php/tshoot_php-set.html



                  Now make sure you have installed composer and other required PHP extensions (install missing PHP extensions). You can check out the system requirements for Magento 2 here:



                  http://devdocs.magento.com/guides/v2.0/install-gde/system-requirements-tech.html



                  Next, check out your files and folder permissions. Magento uses a three-bit mask that you subtract from the UNIX defaults of 666 for files and 777 for directories. Here’s what that means:



                  • 775 for directories, which means full control by the user, complete
                    control by the group, and enables everyone to traverse the directory.
                    Shared hosting providers typically require these permissions.


                  • 664 for files, which means writable by the user, writable by the
                    group, and read-only for everyone else.


                  After making sure of all the above things, migrate your Magento 2 store from one location to another with the following steps:



                  1. Export Magento 2 Database



                  By default, you may have PHPMyAdmin or a similar tool that is capable of exporting your database. Open your database tool and export your Magento 2 database in the .sql file format, because most of the database tools support the .sql file.



                  2. Backup and Transfer Magento 2 Files & Folders



                  After exporting your database, now you will need to download all files & folders of Magento 2 from your current location and upload them to the new location. It might be a time-consuming task, as it depends on how big your Magento 2 store is. If possible, a good approach is to create a zip archive of the files & folders before downloading them.



                  Go to Magento 2 installation directory, create a zip archive of all the files & folders and then download it.



                  Upload the downloaded zip file to the new location and extract it to the new desired destination folder for the Magento 2.



                  3. Import Magento 2 Database



                  Once you have transferred the Magento 2 files & folders, you should import the database to the new server. Go to the PHPMyAdmin, create a new database. Assign credentials to the database or create new username and password for it. In step 1, as we had already exported the database, import the database .sql file into this new database.



                  4. Edit Magento 2 Configurations



                  We are done with exchanging files between both the locations. Now it’s the time to configure your Magento 2 store with your new location. First, you need to edit the app/etc/env.php file with new Magento 2 database configurations according to your new server. Open the env.php file and alter the lines below:



                   ‘db’ =>

                  array (

                  ‘table_prefix’ => ”,

                  ‘connection’ =>

                  array (

                  ‘default’ =>

                  array (

                  ‘host’ => ‘DATABASE_HOST’,

                  ‘dbname’ => ‘DATABASE_NAME’,

                  ‘username’ => ‘DATABASE_USERNAME’,

                  ‘password’ => ‘DATABASE_PASSWORD’,

                  ‘active’ => ‘1’,

                  ),

                  ),

                  ),


                  Where:



                  ‘host’ is the database hostname. Most commonly used host is “localhost”.



                  ‘dbname’ is the database name. Use the one you had created in step 3.



                  ‘username’ is a username that has full privileges to your new database.



                  ‘password’ is the password for that particular database user.



                  New server means new domain name. You have to replace old server domain name with new domain name. For this, you need to modify the value of web/unsecure/base_url and web/secure/base_url in core_config_data table. Enter the new domain name in the value column for both records.



                  5. Clear Magento 2 Cache, Sessions and Deploy Static Content



                  The final step is to clear the Magento 2 cache and deploy static content. Go to following paths and delete everything:



                  ROOT > var > cache > *DELETE ALL*
                  ROOT > var > page_cache > *DELETE ALL*
                  ROOT > var > session > *DELETE ALL*
                  ROOT > pub > static > DELETE ALL EXCEPT .HTACCESS


                  Now, we are setting up static content to deploy on our Magento 2 store. To perform this task, using Command Prompt, navigate to the installation directory of Magento 2 and run the following Magento 2 CLI Command:



                  php bin/magento setup:static-content:deploy




                  If you get any error, check your PHP.EXE and PHP.INI Environment
                  Variable




                  Next, flush Magento cache by running php bin/magento cache:flush in CMD.



                  And finally, to Reindex Magento Static Blocks run php bin/magento indexer:reindex command.



                  You are done with successful migration of Magento 2 store. If you face any issue, do not hesitate to comment!






                  share|improve this answer













                  First of all, make sure that you have set the proper settings in php.ini configuration file. To see the recommended settings, please check this out:



                  http://devdocs.magento.com/guides/v2.0/install-gde/trouble/php/tshoot_php-set.html



                  Now make sure you have installed composer and other required PHP extensions (install missing PHP extensions). You can check out the system requirements for Magento 2 here:



                  http://devdocs.magento.com/guides/v2.0/install-gde/system-requirements-tech.html



                  Next, check out your files and folder permissions. Magento uses a three-bit mask that you subtract from the UNIX defaults of 666 for files and 777 for directories. Here’s what that means:



                  • 775 for directories, which means full control by the user, complete
                    control by the group, and enables everyone to traverse the directory.
                    Shared hosting providers typically require these permissions.


                  • 664 for files, which means writable by the user, writable by the
                    group, and read-only for everyone else.


                  After making sure of all the above things, migrate your Magento 2 store from one location to another with the following steps:



                  1. Export Magento 2 Database



                  By default, you may have PHPMyAdmin or a similar tool that is capable of exporting your database. Open your database tool and export your Magento 2 database in the .sql file format, because most of the database tools support the .sql file.



                  2. Backup and Transfer Magento 2 Files & Folders



                  After exporting your database, now you will need to download all files & folders of Magento 2 from your current location and upload them to the new location. It might be a time-consuming task, as it depends on how big your Magento 2 store is. If possible, a good approach is to create a zip archive of the files & folders before downloading them.



                  Go to Magento 2 installation directory, create a zip archive of all the files & folders and then download it.



                  Upload the downloaded zip file to the new location and extract it to the new desired destination folder for the Magento 2.



                  3. Import Magento 2 Database



                  Once you have transferred the Magento 2 files & folders, you should import the database to the new server. Go to the PHPMyAdmin, create a new database. Assign credentials to the database or create new username and password for it. In step 1, as we had already exported the database, import the database .sql file into this new database.



                  4. Edit Magento 2 Configurations



                  We are done with exchanging files between both the locations. Now it’s the time to configure your Magento 2 store with your new location. First, you need to edit the app/etc/env.php file with new Magento 2 database configurations according to your new server. Open the env.php file and alter the lines below:



                   ‘db’ =>

                  array (

                  ‘table_prefix’ => ”,

                  ‘connection’ =>

                  array (

                  ‘default’ =>

                  array (

                  ‘host’ => ‘DATABASE_HOST’,

                  ‘dbname’ => ‘DATABASE_NAME’,

                  ‘username’ => ‘DATABASE_USERNAME’,

                  ‘password’ => ‘DATABASE_PASSWORD’,

                  ‘active’ => ‘1’,

                  ),

                  ),

                  ),


                  Where:



                  ‘host’ is the database hostname. Most commonly used host is “localhost”.



                  ‘dbname’ is the database name. Use the one you had created in step 3.



                  ‘username’ is a username that has full privileges to your new database.



                  ‘password’ is the password for that particular database user.



                  New server means new domain name. You have to replace old server domain name with new domain name. For this, you need to modify the value of web/unsecure/base_url and web/secure/base_url in core_config_data table. Enter the new domain name in the value column for both records.



                  5. Clear Magento 2 Cache, Sessions and Deploy Static Content



                  The final step is to clear the Magento 2 cache and deploy static content. Go to following paths and delete everything:



                  ROOT > var > cache > *DELETE ALL*
                  ROOT > var > page_cache > *DELETE ALL*
                  ROOT > var > session > *DELETE ALL*
                  ROOT > pub > static > DELETE ALL EXCEPT .HTACCESS


                  Now, we are setting up static content to deploy on our Magento 2 store. To perform this task, using Command Prompt, navigate to the installation directory of Magento 2 and run the following Magento 2 CLI Command:



                  php bin/magento setup:static-content:deploy




                  If you get any error, check your PHP.EXE and PHP.INI Environment
                  Variable




                  Next, flush Magento cache by running php bin/magento cache:flush in CMD.



                  And finally, to Reindex Magento Static Blocks run php bin/magento indexer:reindex command.



                  You are done with successful migration of Magento 2 store. If you face any issue, do not hesitate to comment!







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Aug 16 '17 at 16:33









                  Fayyaz KhattakFayyaz Khattak

                  1,5611022




                  1,5611022



























                      draft saved

                      draft discarded
















































                      Thanks for contributing an answer to Magento Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid


                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.

                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f189259%2fhow-to-configure-an-existing-magento-2-1-7-project-in-another-pc-and-database%23new-answer', 'question_page');

                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      یوتیوب محتویات پیشینه[ویرایش] فناوری‌های ویدئویی[ویرایش] شوخی‌های آوریل[ویرایش] سانسور و فیلترینگ[ویرایش] آمار و ارقامی از یوتیوب[ویرایش] تأثیر اجتماعی[ویرایش] سیاست اجتماعی[ویرایش] نمودارها[ویرایش] یادداشت‌ها[ویرایش] پانویس[ویرایش] پیوند به بیرون[ویرایش] منوی ناوبریبررسی شده‌استYouTube.com[بروزرسانی]"Youtube.com Site Info""زبان‌های یوتیوب""Surprise! There's a third YouTube co-founder"سایت یوتیوب برای چندمین بار در ایران فیلتر شدنسخهٔ اصلیسالار کمانگر جوان آمریکایی ایرانی الاصل مدیر سایت یوتیوب شدنسخهٔ اصلیVideo websites pop up, invite postingsthe originalthe originalYouTube: Overnight success has sparked a backlashthe original"Me at the zoo"YouTube serves up 100 million videos a day onlinethe originalcomScore Releases May 2010 U.S. Online Video Rankingsthe originalYouTube hits 4 billion daily video viewsthe originalYouTube users uploading two days of video every minutethe originalEric Schmidt, Princeton Colloquium on Public & Int'l Affairsthe original«Streaming Dreams»نسخهٔ اصلیAlexa Traffic Rank for YouTube (three month average)the originalHelp! YouTube is killing my business!the originalUtube sues YouTubethe originalGoogle closes $A2b YouTube dealthe originalFlash moves on to smart phonesthe originalYouTube HTML5 Video Playerنسخهٔ اصلیYouTube HTML5 Video Playerthe originalGoogle tries freeing Web video with WebMthe originalVideo length for uploadingthe originalYouTube caps video lengths to reduce infringementthe originalAccount Types: Longer videosthe originalYouTube bumps video limit to 15 minutesthe originalUploading large files and resumable uploadingthe originalVideo Formats: File formatsthe originalGetting Started: File formatsthe originalThe quest for a new video codec in Flash 8the originalAdobe Flash Video File Format Specification Version 10.1the originalYouTube Mobile goes livethe originalYouTube videos go HD with a simple hackthe originalYouTube now supports 4k-resolution videosthe originalYouTube to get high-def 1080p playerthe original«Approximate YouTube Bitrates»نسخهٔ اصلی«Bigger and Better: Encoding for YouTube 720p HD»نسخهٔ اصلی«YouTube's 1080p – Failure Depends on How You Look At It»نسخهٔ اصلیYouTube in 3Dthe originalYouTube in 3D?the originalYouTube 3D Videosthe originalYouTube adds a dimension, 3D goggles not includedthe originalYouTube Adds Stereoscopic 3D Video Support (And 3D Vision Support, Too)the original«Sharing YouTube Videos»نسخهٔ اصلی«Downloading videos from YouTube is not supported, except for one instance when it is permitted.»نسخهٔ اصلی«Terms of Use, 5.B»نسخهٔ اصلی«Some YouTube videos get download option»نسخهٔ اصلی«YouTube looks out for content owners, disables video ripping»«Downloading videos from YouTube is not supported, except for one instance when it is permitted.»نسخهٔ اصلی«YouTube Hopes To Boost Revenue With Video Downloads»نسخهٔ اصلی«YouTube Mobile»نسخهٔ اصلی«YouTube Live on Apple TV Today; Coming to iPhone on June 29»نسخهٔ اصلی«Goodbye Flash: YouTube mobile goes HTML5 on iPhone and Android»نسخهٔ اصلی«YouTube Mobile Goes HTML5, Video Quality Beats Native Apps Hands Down»نسخهٔ اصلی«TiVo Getting YouTube Streaming Today»نسخهٔ اصلی«YouTube video comes to Wii and PlayStation 3 game consoles»نسخهٔ اصلی«Coming Up Next... YouTube on Your TV»نسخهٔ اصلی«Experience YouTube XL on the Big Screen»نسخهٔ اصلی«Xbox Live Getting Live TV, YouTube & Bing Voice Search»نسخهٔ اصلی«YouTube content locations»نسخهٔ اصلی«April fools: YouTube turns the world up-side-down»نسخهٔ اصلی«YouTube goes back to 1911 for April Fools' Day»نسخهٔ اصلی«Simon Cowell's bromance, the self-driving Nascar and Hungry Hippos for iPad... the best April Fools' gags»نسخهٔ اصلی"YouTube Announces It Will Shut Down""YouTube Adds Darude 'Sandstorm' Button To Its Videos For April Fools' Day"«Censorship fears rise as Iran blocks access to top websites»نسخهٔ اصلی«China 'blocks YouTube video site'»نسخهٔ اصلی«YouTube shut down in Morocco»نسخهٔ اصلی«Thailand blocks access to YouTube»نسخهٔ اصلی«Ban on YouTube lifted after deal»نسخهٔ اصلی«Google's Gatekeepers»نسخهٔ اصلی«Turkey goes into battle with Google»نسخهٔ اصلی«Turkey lifts two-year ban on YouTube»نسخهٔ اصلیسانسور در ترکیه به یوتیوب رسیدلغو فیلترینگ یوتیوب در ترکیه«Pakistan blocks YouTube website»نسخهٔ اصلی«Pakistan lifts the ban on YouTube»نسخهٔ اصلی«Pakistan blocks access to YouTube in internet crackdown»نسخهٔ اصلی«Watchdog urges Libya to stop blocking websites»نسخهٔ اصلی«YouTube»نسخهٔ اصلی«Due to abuses of religion, customs Emirates, YouTube is blocked in the UAE»نسخهٔ اصلی«Google Conquered The Web - An Ultimate Winner»نسخهٔ اصلی«100 million videos are viewed daily on YouTube»نسخهٔ اصلی«Harry and Charlie Davies-Carr: Web gets taste for biting baby»نسخهٔ اصلی«Meet YouTube's 224 million girl, Natalie Tran»نسخهٔ اصلی«YouTube to Double Down on Its 'Channel' Experiment»نسخهٔ اصلی«13 Some Media Companies Choose to Profit From Pirated YouTube Clips»نسخهٔ اصلی«Irate HK man unlikely Web hero»نسخهٔ اصلی«Web Guitar Wizard Revealed at Last»نسخهٔ اصلی«Charlie bit my finger – again!»نسخهٔ اصلی«Lowered Expectations: Web Redefines 'Quality'»نسخهٔ اصلی«YouTube's 50 Greatest Viral Videos»نسخهٔ اصلیYouTube Community Guidelinesthe original«Why did my YouTube account get closed down?»نسخهٔ اصلی«Why do I have a sanction on my account?»نسخهٔ اصلی«Is YouTube's three-strike rule fair to users?»نسخهٔ اصلی«Viacom will sue YouTube for $1bn»نسخهٔ اصلی«Mediaset Files EUR500 Million Suit Vs Google's YouTube»نسخهٔ اصلی«Premier League to take action against YouTube»نسخهٔ اصلی«YouTube law fight 'threatens net'»نسخهٔ اصلی«Google must divulge YouTube log»نسخهٔ اصلی«Google Told to Turn Over User Data of YouTube»نسخهٔ اصلی«US judge tosses out Viacom copyright suit against YouTube»نسخهٔ اصلی«Google and Viacom: YouTube copyright lawsuit back on»نسخهٔ اصلی«Woman can sue over YouTube clip de-posting»نسخهٔ اصلی«YouTube loses court battle over music clips»نسخهٔ اصلیYouTube to Test Software To Ease Licensing Fightsthe original«Press Statistics»نسخهٔ اصلی«Testing YouTube's Audio Content ID System»نسخهٔ اصلی«Content ID disputes»نسخهٔ اصلیYouTube Community Guidelinesthe originalYouTube criticized in Germany over anti-Semitic Nazi videosthe originalFury as YouTube carries sick Hillsboro video insultthe originalYouTube attacked by MPs over sex and violence footagethe originalAl-Awlaki's YouTube Videos Targeted by Rep. Weinerthe originalYouTube Withdraws Cleric's Videosthe originalYouTube is letting users decide on terrorism-related videosthe original«Time's Person of the Year: You»نسخهٔ اصلی«Our top 10 funniest YouTube comments – what are yours?»نسخهٔ اصلی«YouTube's worst comments blocked by filter»نسخهٔ اصلی«Site Info YouTube»نسخهٔ اصلیوبگاه YouTubeوبگاه موبایل YouTubeوووووو

                      Magento 2 - Auto login with specific URL Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Customer can't login - Page refreshes but nothing happensCustom Login page redirectURL to login with redirect URL after completionCustomer login is case sensitiveLogin with phone number or email address - Magento 1.9Magento 2: Set Customer Account Confirmation StatusCustomer auto connect from URLHow to call customer login form in the custom module action magento 2?Change of customer login error message magento2Referrer URL in modal login form

                      Rest API with Magento using PHP with example. Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?How to update product using magento client library for PHP?Oauth Error while extending Magento Rest APINot showing my custom api in wsdl(url) and web service list?Using Magento API(REST) via IXMLHTTPRequest COM ObjectHow to login in Magento website using REST APIREST api call for Guest userMagento API calling using HTML and javascriptUse API rest media management by storeView code (admin)Magento REST API Example ErrorsHow to log all rest api calls in magento2?How to update product using magento client library for PHP?