Note:

Eseosa -what we did today was look at mysql dump and I changed the database back and forth from my local one to the one that Eseosa had set-up.


In 

/var/www/moodle 


Then vi the config.php and this is where the database information is stored. 


Here we can change the database name and the database password  I am able to switch this information and have the instance connect to the database that I needed it to this is helpful if we are wanting to try different versions of moodle and debug using the same database information so that that we know its the same (even though the databases are different)


Naturally doing a mysql dump created a new database called moodle. To stop this we have the no create db flag. 



Video Link:

https://drive.google.com/file/d/1qmRswM-9rVP2uDOxC6uHqDwdsl-Fz-hP/view?usp=sharing



In this video we cover:

  1. Reconfigured a restored site using a snapshot
    1. local MYSQL
    2. local NGINX/FPM
      1. Changed server name field in sites-enabled/moodle
      2. Changed wwwroot value in <moodle_root>/config.php
  2. MYSQLDUMP
    1. Worked through dumping a database to file
      1. Discussed briefly dump parameters 
    2. Worked through modifying/editing a database dump file
  3. MYSQL Restore
    1. Worked through restoring a database instance to an EXTERNAL RDS using a dump file
    2. Worked through restoring same dump file to another database instance within the same database server
    3. Worked through re-configuring a moodle site to use new database connection string from (3a and 3b)
  4. Dealing with database conflict