aerotore.blogg.se - Timecamp change colors

#TIMECAMP CHANGE COLORS INSTALL#
#TIMECAMP CHANGE COLORS UPDATE#

Copy config files instead of linking them.Pro-tip, drop database wordpress_develop in phpMyAdmin followed by vagrant provision clears your for reinstall. Databases can now be dropped in phpMyAdmin.Begin implementing best practices from Google's shell style guide in our provisioning scripts.Happy Fix vagrant up after halt meets expectations and no longer requires provisioning to be reapplied.Introduce Auto Site Setup during provisioning to allow for easy new project configuration.Add zip as a package during provisioning.Use a new global composer configuration.Add -allow-root to all wp-cli calls in VVV core.Transition to Varying Vagrant Vagrants organization.

#TIMECAMP CHANGE COLORS INSTALL#

Nginx: Install using the mainline repository, currently 1.7.x.

Logs: Map a shared directory for logs, start storing php_errors.log.

#TIMECAMP CHANGE COLORS UPDATE#

NodeJS: Self update NPM during provisioning.

NodeJS: Use recommended PPAs to install.

Bash: Allow for a custom bash_prompt file in config/.

VVV Dashboard: Add Opcache Status for opcache monitoring.

PHP: Install XDebug PECL extension directly, rather than via apt.PHP: Start tracking custom opcache.ini file.WordPress: Add develop_git to convert the default SVN checkout to Git.See #373 and #370 for reasoning and discussion. Due to this change, something like cd "$(dirname $0)" no longer works as expected. Init scripts are now fired with source rather than bash.If you are connecting via SSH through an application that relies on your machines known_hosts file, you will need to clear the old key for 192.168.50.4. With a new operating system comes a new RSA key.Running vagrant box list will show you all base VMs on your local machine.

If you'd like to free space, remove the old box with vagrant box remove precise32. A new box will be downloaded for the base virtual machine.A full vagrant destroy is recommended for best results.Possible Breaking: Ubuntu has been upgraded from 12.04 LTS to 14.04 LTS.A db_backup script is provided by default that creates local backups of each database on halt, suspend, and destroy if the vagrant-triggers plugin is installed.Database data will no longer exist on the virtual machine after vagrant destroy.Database data will continue to exist on the virtual machine through vagrant halt and vagrant suspend.If database files already exist from an earlier version of VVV, data will continue to be mapped locally until removed.A full vagrant destroy and the removal of MySQL data from /database/data/ is recommended.Possible Breaking: By default, database files are no longer mapped to a local location.New: Add support for Parallels as a provider.Varying Vagrant Vagrants Changelog In Progress