VVV v
- Title 1
+Subtitle 3
+Title 2
+Subtitle 4
+Title 3
+Subtitle 5
+You can find a Sequel Pro/Sequel Ace connection file at database/sql/sequelpro.spf. For the default database credentials see the following:
You can manually back up databases by running the command vagrant ssh -c "db_backup", and VVV will place SQL files in the database/sql VVV sub-folder.
Backups can be manually restored using vagrant ssh -c "db_restore".
If you have problems, updating and runnning vagrant up --provision usually fixes them, but if you have a problem you can't solve, you should let the VVV team know. Don't spend hours figuring out a problem we can fix in minutes.
+ + VVV Documentation + + + Get Help on GitHub + + + Join the VVV Slack + +
+If provisioning does not work correctly, and you don't have the terminal output, you can find logs in the logs/provisioners subfolder, arranged by time and date.
You can also find PHP error logs in logs/php.
sudo command!
+
+
+ This will cause lots of problems, back up your database, destroy your virtual machine, and erase the .vagrant folder, as well as any root owned virtual machine files and folders, then reprovision VVV without sudo.
To fix this, these commands must be done in this order.
+mysqldump, use the built in backup script, or PHPMyAdmin.sudo vagrant halt to power down VVV.sudo vagrant destroy --force to destroy the VM..vagrant subfolder.whoami will tell you the user to change ownership to.vagrant up without using sudo, if this fails, search for virtualbox and vagrant files across your system that have not been cleaned up.sudo again. Not even just in case.In the future we will be adding more roadblocks to prevent normal usage of VVV while under root. E.g. sites will refuse to provision, features will disable themselves, etc.
+By continuing to use VVV with sudo you will be unable to request support for anything other than fixing this issue.
{ site.description }
: null + } ++ { id } +
++ { site.description ? site.description : null } +
+Information about this site, its folder location, PHP version etc
+ +| VM folder Location: | +/srv/www/{id} |
+
| Host folder Location: | +www/{id} |
+
| Provisioner git repository URL: | +{site.repo ? site.repo : 'none'} |
+
| Provisioner logs: | +{ `logs/provisioners/{time-of-provision}/provision-${id}.log` } |
+
This is the JSON version of what VVV sees for this site:
+
+ { JSON.stringify( site, null, 4 ) }
+
+ To add a new site, update the sites section of config/config.yml then run vagrant provision to apply the changes.
For more details on what to add and examples, see the documentation here:
++ + VVV Docs: Adding a new site + + + VVV Docs: Adding an existing site + +
+