zepgram / magento2-fast-vm Goto Github PK
View Code? Open in Web Editor NEWOptimal vagrant developer box for Magento2. Folders synced by nfs/rsync. This box includes Magento developer utilities.
License: MIT License
Optimal vagrant developer box for Magento2. Folders synced by nfs/rsync. This box includes Magento developer utilities.
License: MIT License
I've run vagrant up with rsync in setting and i get this error :
dev2.xxxxxxxx.com: vagrant rsync-back dev2.xxxxxxxx.com | vagrant rsync-auto --rsync-chown dev2.xxxxxxxx.com
dev2.xxxxxxxx.com: An invalid option was specified. The help for this command
dev2.xxxxxxxx.com: is available below.
dev2.xxxxxxxx.com:
dev2.xxxxxxxx.com: Usage: vagrant rsync-back [vm-name]
I've modded dependency.rb to try to use VM machine name but i get the same error.
Is it possible that a space in machine name could make this error ?
Kind regards
Hi, I have setup this skeleton to easily debug on my localhost a magento installation. However after following the instructions from https://xdebug.org/wizard and use the following steps but when done I do not see the xdebug either php -v
or via http://192.168.200.0/php/
sudo apt-get install php-dev autoconf automake
curl -O http://xdebug.org/files/xdebug-2.9.0.tgz
tar -xvzf xdebug-2.9.0.tgz
cd xdebug-2.9.0
phpize
./configure
make
sudo cp modules/xdebug.so /usr/lib/php/20180731
echo 'zend_extension = /usr/lib/php/20180731/xdebug.so' | sudo tee -a /etc/php/7.3/fpm/php.ini
and then restart nginx and php-fpm
sudo /etc/init.d/nginx restart
sudo /etc/init.d/php7.3-fpm restart
any help would be much appreciated!
I am having an issue where the chown command is NOT affecting the ownership of '/home/vagrant/magento'.
My Computer and VB/Vagrant: Mac OSX, Vagrant 2.2.7, VirtualBox Version 5.2.26 r128414 (Qt5.6.3)
Here is how I have the config.yaml file setup:
vmconf:
machine_name: 'Vagrant Magento 2'
network_ip: '192.168.60.6'
host_name: 'local'
memory: '4096'
cpus: '1'
mount: 'nfs'
path: 'root'
provision: 'all'
composer:
username: 'omitted'
password: 'omitted'
git:
name: 'omitted'
email: '[email protected]'
host: 'magento.cloud'
repository: 'ssh://[email protected]:omitted.git'
magento:
url: 'magento.leupold.test'
source: 'integration'
edition: 'enterprise'
version: '2.3.4'
php_version: 'default'
sample: 'true'
mode: 'developer'
currency: 'USD'
language: 'en_US'
time_zone: 'America/Los_Angeles'
crypt_key: ''
Pretty standard, except I am hoping to checkout the integration branch of our magento cloud repo.
The issue doesn't seem to get as far as checking pout from our repo, I get an error during the "Magento pre-installation sequence". Here is what I see:
local: chown:
local: changing ownership of '/home/vagrant/magento'
local: : Operation not permitted
This causes the, "Magento Installation Sequence" to fail:
local: --- Magento installation sequence ---
local: Cloning into '/home/vagrant/magento'...
local: fatal: No path specified. See 'man git-pull' for valid url syntax
local: fatal: Not a git repository (or any parent up to mount point /home/vagrant/magento)
local: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
local: fatal: Not a git repository (or any parent up to mount point /home/vagrant/magento)
local: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
local: Composer could not find a composer.json file in /home/vagrant/magento
local: To initialize a project, please create a composer.json file as described in the https://getcomposer.org/ "Getting Started" section
local: chmod:
local: cannot access '/home/vagrant/magento/bin/magento'
local: : No such file or directory
local: sudo
local: :
local: /home/vagrant/magento/bin/magento: command not found
local: sudo
local: :
I vagrant ssh in after the errors to try the chown command used in the "Magento pre-installation sequence".
chown -R vagrant:vagrant /home/vagrant
Running this from the /home/vagrant directory, nothing happens!
If I run:
sudo chown -R vagrant:vagrant /home/vagrant
I get:
chown: changing ownership of './magento': Operation not permitted
Am I missing something here? I am using the NFS setting on a Mac. I have used synced folders in the past with no issue.
zepgram: You might want to run 'apt --fix-broken install' to correct these.
zepgram: The following packages have unmet dependencies:
zepgram: percona-release : Depends: gnupg2 but it is not installed
zepgram: E
zepgram: :
zepgram: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
Process finished with exit code 1
I think need to edit 38 line in 010-system-packages.sh
replace 'vim git git-flow' > 'vim git git-flow gnupg2'
After clean install with this latest box I got the following error:
-- Unit nginx.service has begun starting up.
Oct 26 11:11:45 zepgram nginx[24775]: nginx: [emerg] open() "/home/vagrant/extra/magento.nginx.conf" failed (2: No such file or directory) in /etc/nginx/sites-enab
Oct 26 11:11:45 zepgram nginx[24775]: nginx: configuration file /etc/nginx/nginx.conf test failed
This file is present in the host project with .
host is ubuntu 16
config file:
vmconf:
machine_name: 'Vagrant Magento 2'
network_ip: '192.168.200.50'
host_name: 'zepgram'
memory: '4096'
cpus: '2'
mount: 'nfs'
path: 'root'
provision: 'all'
composer:
username: '-'
password: '-'
git:
name: '-'
email: '-'
host: '-'
repository: '-'
magento:
url: '-'
source: 'development'
edition: 'community'
version: '2.4.0'
php_version: 'default'
sample: 'false'
mode: 'development'
currency: 'EUR'
language: 'nl_NL'
time_zone: 'Europe/Amsterdam'
crypt_key: '-'
Hello zepgram,
I don't understand how the nginx docroot is configured on my machine.
When I type the name of my server or ip address in the browser I just have the Nginx homepage displayed for now.
If I search in the browser for exisiting sub-folders in my home magento directory I get 404 errors.
How do I make it link to the cd directory /home/vagrant/magento/?
Thanks!
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "0f6e86f8-562a-4356-b4b1-9bac72ff552a", "--type", "headless"]
Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2' (VERR_INTNET_FLT_IF_NOT_FOUND).
VBoxManage.exe: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
Hello zepgram,
I've had today a forced virtual box update to 6.1.4 version (I had previously the 6.0.18) and now I have an error on vagrant up and get stuck:
==> zepgram: Clearing any previously set network interfaces...
vagrant : A host only network interface you're attempting to configure via DHCP
In Zeile:1 Zeichen:1
+ vagrant up
+ ~~~~~~~~~~
+ CategoryInfo : NotSpecified: (A host only net...figure via DHCP:String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
already has a conflicting host only adapter with DHCP enabled. The
DHCP on this adapter is incompatible with the DHCP settings. Two
host only network interfaces are not allowed to overlap, and each
host only network interface can have only one DHCP server. Please
reconfigure your host only network or remove the virtual machine
using the other host only network.
Did you already have something similar, could you help me to resolve this? Thanks
I have tried twice to boot this VM but both times I run into the same problem.
PHP Fatal error: Uncaught Error: Class 'Composer\Autoload\ComposerStaticInit6fd50736163f37222d3a28779c21eaf9' not found in /srv/magento/vendor/composer/autoload_real.php:34
I've attached my console log (well as far back as it would go) in case there is anything in that which could help.
console-error-during-vagrant-up.txt
I've followed all the steps in the readme.md and as far as I can tell, have done everything correctly.
Hello, I am looking for a dev setup where it will be very easy to clone an existing working dev magento2 install and database and get the 2nd one up and running very quickly, like in 5 minutes. Is that possible with this package?
What is the process to do that?
Thanks!
after deploy project from repository i got an error( mount: 'rsync'):
1 exception(s):
Exception #0 (Magento\Framework\Exception\FileSystemException): The path "/home/vagrant/magento/pub/static/." is not writable.
adding this code to vagrantfile solves problem:
config.bindfs.default_options = {
force_user: 'vagrant',
force_group: 'www-data',
perms: 'u=rwx:g=rwx:o=rx'
}
Hi zepgram,
I can't run any more my Magento 2 virtual machine on the command line under Windows Powershell since a big Windows update.
I always get the following error:
> vagrant up
==> All dependencies are satisfied
C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:158:in 'rescue in execute': Zugriff verweigert (5) (Vagrant::Util::Subprocess::LaunchError)
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:151:in `execute'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:22:in `execute'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:115:in `execute_cmd'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/platform.rb:82:in `block in windows_admin?'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/platform.rb:84:in `windows_admin?'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/hyperv/provider.rb:20:in `usable?'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:361:in `block in default_provider'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:49:in `block in each'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:48:in `each'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:48:in `each'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:347:in `default_provider'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:943:in `guess_provider'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:955:in `find_configured_plugins'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:983:in `process_configured_plugins'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:178:in `initialize'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/bin/vagrant:145:in `new'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/bin/vagrant:145:in `<main>'
Here is my setup:
Windows 10 Pro
Vagrant 2.2.7
Virtual Box 6.0.16
I also tried to launch run vagrant on Powershell administrator and Git bash.
It has run but I still got the same error at the script:
==> zepgram: rsync-back and rsync auto triggered...
==> zepgram: Duration: ~10min. Install is done when rsync-auto will start watching.
zepgram: Running local: Inline script
zepgram: vagrant rsync-back zepgram | vagrant rsync-auto --rsync-chown zepgram
zepgram: C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:158:in `rescue in execute': Zugriff verweigert (5) (Vagrant::Util::Subprocess::LaunchError)
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:151:in `execute'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:22:in `execute'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:174:in `version'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:195:in `validate_install!'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:96:in `execute_cmd'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/platform.rb:82:in `block in windows_admin?'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/platform.rb:84:in `windows_admin?'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/hyperv/provider.rb:20:in `usable?'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:361:in `block in default_provider'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:49:in `block in each'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:48:in `each'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:48:in `each'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:347:in `default_provider'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:943:in `guess_provider'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:955:in `find_configured_plugins'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:983:in `process_configured_plugins'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:178:in `initialize'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/bin/vagrant:145:in `new'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/bin/vagrant:145:in `<main>'
zepgram:
zepgram: C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:158:in `rescue in execute': Zugriff verweigert (5) (Vagrant::Util::Subprocess::LaunchError)
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:151:in `execute'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:22:in `execute'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:174:in `version'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:195:in `validate_install!'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:96:in `execute_cmd'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/platform.rb:82:in `block in windows_admin?'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/platform.rb:84:in `windows_admin?'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/hyperv/provider.rb:20:in `usable?'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:361:in `block in default_provider'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:49:in `block in each'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:48:in `each'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:48:in `each'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:347:in `default_provider'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:943:in `guess_provider'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:955:in `find_configured_plugins'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:983:in `process_configured_plugins'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:178:in `initialize'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/bin/vagrant:145:in `new'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/bin/vagrant:145:in `<main>'
zepgram:
==> zepgram: Trigger run failed
==> zepgram: A script exited with an unacceptable exit code 1.
A script exited with an unacceptable exit code 1.
Could you please help me solve this error?
Thanks!
Hi, I would like to try your pre-configured VM. Versions:
Errors:
zepgram: [Progress: 655 / 1314]
zepgram: Installing search configuration...
zepgram: In SearchConfig.php line 81:
zepgram:
zepgram: Could not validate a connection to Elasticsearch. No alive nodes found in your cluster
...
zepgram: Updating modules:
zepgram: Could not validate a connection to Elasticsearch. No alive nodes found in your cluster
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
I tried mount: nfs, rsync and default and path: root and app and I didn't open explorer during installation. Everytime the same error.
How can I finish the setup manually and check/reactivate Elasticsearch later?
Thanks for your help!
Hello,
Perhaps you may have an idea of what is happening here. I was able to manually get things running which I will mention at the the end.
zepgram: [Progress: 1314 / 1314]
zepgram: [SUCCESS]: Magento installation complete.
zepgram: [SUCCESS]: Magento Admin URI: /admin
zepgram: Nothing to import.
zepgram: <warning>Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/</warning>
zepgram: ./composer.json has been updated
zepgram: Loading composer repositories with package information
zepgram: <warning>Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/</warning>
zepgram: Updating dependencies (including require-dev)
zepgram: Package operations: 20 installs, 0 updates, 0 removals
zepgram: - Installing magento/module-catalog-sample-data (100.4.0):
zepgram: Downloading
zepgram: (100%)
zepgram: Installing "magento/composer-root-update-plugin: 1.1.2" for the Web Setup Wizard
zepgram: Loading composer repositories with package information
zepgram: <warning>Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/</warning>
zepgram: Updating dependencies
zepgram: /tmp/vagrant-shell: line 82: 6387 Killed sudo -u vagrant php -d memory_limit=-1 "$PROJECT_PATH"/bin/magento sampledata:deploy
zepgram: Cache types config flushed successfully
zepgram: Cache cleared successfully
zepgram: File system cleanup:
zepgram: /home/vagrant/magento/generated/code/Composer
zepgram: /home/vagrant/magento/generated/code/Dotdigitalgroup
zepgram: /home/vagrant/magento/generated/code/Magento
zepgram: /home/vagrant/magento/generated/code/PayPal
zepgram: /home/vagrant/magento/generated/code/Psr
zepgram: /home/vagrant/magento/generated/code/Symfony
zepgram: /home/vagrant/magento/generated/code/Yotpo
zepgram: The directory '/home/vagrant/magento/generated/metadata/' doesn't exist - skipping cleanup
zepgram: /home/vagrant/magento/pub/static/deployed_version.txt
zepgram: Updating modules:
zepgram: Could not validate a connection to Elasticsearch. No alive nodes found in your cluster
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
Also missing:
Jun 23 19:52:47 zepgram systemd[1]: Starting A high performance web server and a reverse proxy server...
Jun 23 19:52:48 zepgram nginx[7090]: nginx: [emerg] open() "/home/vagrant/extra/magento.nginx.conf" failed (2: No such file or directory) in /etc/ngi
Jun 23 19:52:48 zepgram nginx[7090]: nginx: configuration file /etc/nginx/nginx.conf test failed
Jun 23 19:52:48 zepgram systemd[1]: nginx.service: Control process exited, code=exited status=1
Jun 23 19:52:48 zepgram systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Jun 23 19:52:48 zepgram systemd[1]: nginx.service: Unit entered failed state.
Jun 23 19:52:48 zepgram systemd[1]: nginx.service: Failed with result 'exit-code'.
Now, for how I was able to get it running post failure.
1.) I immediately ssh'd into the box, running bin/magento setup:upgrade
2.) then created a `/home/vagrant/extra/magento.nginx.conf with a sample config with this content: https://raw.githubusercontent.com/magento/magento2/2.4-develop/nginx.conf.sample
Any ideas why it fails at that point mentioned above? Thanks in advance for your help.
Hi there, I am consistently getting below error. I reinstall a few times. It only worked once and never since.
I can still ssh in but nothing works. I am on Mac.
Going on, assuming VBoxService is correct...
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules. This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Kernel headers not found for target kernel
4.9.0-14-amd64. Please install them and execute
/sbin/rcvboxadd setup
modprobe vboxguest failed
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
/sbin/rcvboxadd setup
Stdout from the command:
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules. This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Kernel headers not found for target kernel
4.9.0-14-amd64. Please install them and execute
/sbin/rcvboxadd setup
Stderr from the command:
modprobe vboxguest failed
The log file /var/log/vboxadd-setup.log may contain further information.
Hello,
I got an error for Elasticsearch when I try to install Magento 2 in the virtual machine it was something like this:
Could not validate a connection to Elasticsearch. No alive nodes found in y zepgram: our cluster
I was able to fix by adding this parameter --elasticsearch-host='127.0.0.1'
to the setup:install command in provision/110-magento-app.sh
Thank you!
Got this error during installation:
This is the content of my config.yaml (unchanged from original except for Magento credentials):
vmconf:
machine_name: 'Vagrant Magento 2'
network_ip: '192.168.200.50'
host_name: 'zepgram'
memory: '4096'
cpus: '1'
mount: 'nfs'
path: 'root'
provision: 'all'
composer:
username: 'removed'
password: 'removed'
git:
name: 'John Doe'
email: '[email protected]'
host: 'github.com'
repository: 'ssh://[email protected]:project-name.git'
magento:
url: 'dev.magento.com'
source: 'composer'
edition: 'community'
version: '2.3.2'
php_version: 'default'
sample: 'true'
mode: 'developer'
currency: 'USD'
language: 'en_US'
time_zone: 'America/New_York'
need to create multiple stores with the same domain:
site.com/en/
site.com/fr/
site.com/de/
I changed magento.ngnix.conf (added fastcgi_param MAGE_RUN_CODE 'en'; fastcgi_param MAGE_RUN_TYPE store;), but I get a 404 error().
do you have any ideas?
Hi - it seems that perhaps an apt-get update is needed somewhere..? The following is the output from bringing up the VM:
c:\Users\Kenny\Documents\GitHub\magento2-fast-vm>vagrant up
Checking dependencies...
apt-get install -y linux-headers-uname -r
dkms
Stdout from the command:
Reading package lists...
Building dependency tree...
Reading state information...
Stderr from the command:
E: Unable to locate package linux-headers-4.9.0-9-amd64
E: Couldn't find any package by glob 'linux-headers-4.9.0-9-amd64'
E: Couldn't find any package by regex 'linux-headers-4.9.0-9-amd64'
c:\Users\Kenny\Documents\GitHub\magento2-fast-vm>
Hi I was able to install this box. But it seems that the files that I copied didn't take effect and eventhough I changed the DB to use our existing DB it's still throwing an error.
I have this error when refreshing the page
1 exception(s):
Exception #0 (Exception): Notice: Undefined index: in /srv/magento/vendor/magento/module-developer/Model/View/Page/Config/RendererFactory.php on line 70
Exception #0 (Exception): Notice: Undefined index: in /srv/magento/vendor/magento/module-developer/Model/View/Page/Config/RendererFactory.php on line 70
zepgram: --- Magento installation sequence ---
zepgram: sudo
zepgram: :
zepgram: composer: command not found
zepgram: sudo
zepgram: :
zepgram: composer: command not found
zepgram: sudo
zepgram: :
zepgram: composer: command not found
zepgram: chmod:
zepgram: cannot access '/home/vagrant/magento/bin/magento'
zepgram: : No such file or directory
zepgram: sudo
zepgram: :
zepgram: /home/vagrant/magento/bin/magento: command not found
zepgram: sudo
zepgram: :
zepgram: /home/vagrant/magento/bin/magento: command not found
The SSH command responded with a non-zero exit status.
Am I missing something to install composer?
It's my first time installing Magento and I have tackled challenge by challenge but this one is stumping me a bit.
I'm getting permission issues when getting to the point of installing Magento.
Editorially cleaned up I'm getting something like
local.magento2: - Installing magento/project-community-edition (2.4.2):
local.magento2: Downloading
local.magento2: [RuntimeException]
local.magento2: Could not delete /home/vagrant/magento/:
local.magento2: Composer could not find a composer.json file in /home/vagrant/magento
local.magento2: To initialize a project, please create a composer.json file as described in the https://getcomposer.org/ "Getting Started" section
local.magento2: cp:
local.magento2: cannot create regular file '/home/vagrant/magento/auth.json'
local.magento2: : Permission denied
local.magento2: chmod:
local.magento2: cannot access '/home/vagrant/magento/bin/magento'
local.magento2: : No such file or directory
local.magento2: sudo
local.magento2: /home/vagrant/magento/bin/magento: command not found
local.magento2: sudo
local.magento2: /home/vagrant/magento/bin/magento: command not found
local.magento2: Could not open input file: /home/vagrant/magento/bin/magento
local.magento2: sudo
local.magento2: /home/vagrant/magento/bin/magento: command not found
The permission in as follows
drwxr-xr-x 2 vagrant vagrant 4096 May 9 02:38 extra
drwxr-xr-x 2 501 www-data 64 May 9 14:45 magento
drwxr-xr-x 2 vagrant vagrant 4096 May 9 03:30 .nano
The magento folder is empty
the auth.json file is in /home/vagrant
in my config yaml I have
mount: 'nfs'
path: '/var/www/magento'
provision: 'magento'
Any idea of what needs to happen?
I get an error installing for Magento 2.4.2 on MacOS 10.15.7 (Catalina).
I used the master branch.
I tried to change the hostDirectory in the VagrantFile but it failed. The script tried again to mount the same host directory (/home/vagrant/magento). Maybe there are others locations to change this hostDirectory variable ? Or the solution is elsewhere ?
Hello,
I've try twice to setup the VM. All setup is good. Magento front is working but i cannot get backend page. each time i get 404 error page.
I've tried to change "admin" backend frontname without success with :
php bin/magento setup:config:set --backend-frontname="DSFgSsS45"
I try this too without success :
php -f bin/magento cache:flush
sudo rm -rf var/cache var/generation var/page_cache
php -f bin/magento cache:disable
chmod -R 777 var
chmod -R 777 pub
chmod -R 777 generated
When i try to change with chmod the folder autorization doesn't change :
BEFORE : drwxrwxr-- 13 vagrant www-data 416 Jul 21 12:17 pub
AFTER : drwxrwxr-- 13 vagrant www-data 416 Jul 21 12:17 pub
PS : I'm using this settings :
magento:
url: 'dev.xxxxx.com'
source: 'composer'
edition: 'community'
version: '2.3.5'
php_version: 'default'
sample: 'true'
mode: 'developer'
currency: 'EUR'
language: 'en_US'
time_zone: 'Europe/Paris'
crypt_key: ''
Thanks
I'm trying to upload images of product but I get an error(tested in m2.4.2): 'A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later.'
system.log: main.CRITICAL: The permissions can't be changed for the "/home/vagrant/magento/pub/media/tmp/catalog/product/u/n/u.jpg" path. Warning!chmod(): Operation not permitted. [] []
My process stuck during installation. I already tried different configurations( uncomment # v.gui=true, different config files). With and without mage2.
I also create new ssh without pass, but still crashing. If I install just system it will install the box, but i cant install magento2 on the box. I am running vagrant 2.2.0 and VB 5.2.2 on windows 10 pro.
I see a lot of these warnings:
zepgram: Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/
But ultimately this is the error:
zepgram: Writing lock file
zepgram: Generating autoload files
zepgram: 20 packages you are using are looking for funding.
zepgram: Use the `composer fund` command to find out more!
zepgram: Use the composer fund
command to find out more!
zepgram: - Installing magento/module-bundle-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-theme-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-cms-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-customer-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-downloadable-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-grouped-product-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-msrp-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-offline-shipping-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-product-links-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-review-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-catalog-rule-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-sales-rule-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-configurable-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-sales-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-swatches-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-tax-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-widget-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/module-wishlist-sample-data (100.4.0): Downloading (100%)
zepgram: - Installing magento/sample-data-media (100.4.0): Downloading (100%)
zepgram:
zepgram: Installation failed, reverting ./composer.json to its original content.
zepgram:
zepgram: In FilesystemRepository.php line 63:
zepgram:
zepgram: Invalid repository data in /home/vagrant/magento/vendor/composer/installed.
zepgram: json, packages could not be loaded: [Seld\JsonLint\ParsingException] "/home
zepgram: /vagrant/magento/vendor/composer/installed.json" does not contain valid JSO
zepgram: N
zepgram: Parse error on line 1:
zepgram: There is an error during sample data deployment. Composer file will be reverted.
zepgram:
zepgram: ^
zepgram: Expected one of: 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '['
zepgram:
zepgram:
zepgram: require [--dev] [--prefer-source] [--prefer-dist] [--fixed] [--no-progress] [--no-suggest] [--no-update] [--no-scripts] [--update-no-dev] [--update-with-dependencies] [--update-with-all-dependencies] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--skip-magento-root-plugin] [--use-default-magento-values] [--interactive-magento-conflicts] [--base-magento-edition BASE-MAGENTO-EDITION] [--base-magento-version BASE-MAGENTO-VERSION] [--] [...]
zepgram:
zepgram: Can't run this operation: deployment configuration is absent. Run 'magento setup:config:set --help' for options.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
It seems to be consistent - have retried a few times, same error
Everything had been working fine for me until yesterday's updates and now it fails whenever I run the vagrant up command.
Here are the contents from my config.yaml file
vmconf:
machine_name: 'Vagrant Magento 2'
network_ip: '192.168.200.50'
host_name: 'zepgram'
memory: '4096'
cpus: '1'
mount: 'nfs'
path: 'root'
provision: 'all'
composer:
username: '----removed----'
password: '----removed----'
git:
name: 'DeanMorganMB'
email: '[email protected]'
host: 'github.com'
repository: 'ssh://[email protected]:project-name.git'
magento:
url: 'dev.magento.com'
source: 'composer'
edition: 'community'
version: '2.3.1'
php_version: 'default'
sample: 'true'
mode: 'developer'
currency: 'GBP'
language: 'en_GB'
time_zone: 'Europe/London'
Any help would be appreciated.
please add the ability to change the version php (magento 2.3.0 use php>7.0)
Hello,
I'm currently stuck during the Magento installation process because of the magento-composer-installer plugin. I also did a system installation and then used the following command from the magento devdocs, but I always get the same error:
composer --no-ansi --no-interaction install --no-progress --prefer-dist --optimize-autoloader
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Finished: success: 0, skipped: 0, failure: 334, total: 334
Package operations: 460 installs, 0 updates, 0 removals
- Installing magento/magento-composer-installer (0.1.13): Loading from cache
Plugin installation failed, rolling back
- Removing magento/magento-composer-installer (0.1.13)
[RuntimeException]
Could not delete /home/vagrant/magento/magento2/vendor/magento/magento-composer-installer/src/MagentoHackathon:
I'm using Windows 10 as host machine.
Composer 1.9.2
PHP 7.2
Vagrant 2.2.6
Virtual Box 6.0.16
Do you have any idea how to resolve that error?
Thanks
Hi zepgram,
I can't run any more my Magento 2 virtual machine on the command line under Windows Powershell since a big Windows update.
I always get the following error:
> vagrant up
==> All dependencies are satisfied
C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:158:in 'rescue in execute': Zugriff verweigert (5) (Vagrant::Util::Subprocess::LaunchError)
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:151:in `execute'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:22:in `execute'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:115:in `execute_cmd'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/platform.rb:82:in `block in windows_admin?'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/platform.rb:84:in `windows_admin?'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/hyperv/provider.rb:20:in `usable?'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:361:in `block in default_provider'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:49:in `block in each'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:48:in `each'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:48:in `each'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:347:in `default_provider'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:943:in `guess_provider'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:955:in `find_configured_plugins'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:983:in `process_configured_plugins'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:178:in `initialize'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/bin/vagrant:145:in `new'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/bin/vagrant:145:in `<main>'
Here is my setup:
Windows 10 Pro
Vagrant 2.2.7
Virtual Box 6.0.16
I also tried to launch run vagrant on Powershell administrator and Git bash.
It has run but I still got the same error at the script:
==> zepgram: rsync-back and rsync auto triggered...
==> zepgram: Duration: ~10min. Install is done when rsync-auto will start watching.
zepgram: Running local: Inline script
zepgram: vagrant rsync-back zepgram | vagrant rsync-auto --rsync-chown zepgram
zepgram: C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:158:in `rescue in execute': Zugriff verweigert (5) (Vagrant::Util::Subprocess::LaunchError)
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:151:in `execute'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:22:in `execute'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:174:in `version'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:195:in `validate_install!'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:96:in `execute_cmd'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/platform.rb:82:in `block in windows_admin?'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/platform.rb:84:in `windows_admin?'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/hyperv/provider.rb:20:in `usable?'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:361:in `block in default_provider'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:49:in `block in each'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:48:in `each'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:48:in `each'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:347:in `default_provider'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:943:in `guess_provider'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:955:in `find_configured_plugins'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:983:in `process_configured_plugins'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:178:in `initialize'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/bin/vagrant:145:in `new'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/bin/vagrant:145:in `<main>'
zepgram:
zepgram: C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:158:in `rescue in execute': Zugriff verweigert (5) (Vagrant::Util::Subprocess::LaunchError)
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:151:in `execute'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/subprocess.rb:22:in `execute'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:174:in `version'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:195:in `validate_install!'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/powershell.rb:96:in `execute_cmd'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/platform.rb:82:in `block in windows_admin?'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/platform.rb:84:in `windows_admin?'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/hyperv/provider.rb:20:in `usable?'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:361:in `block in default_provider'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:49:in `block in each'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:48:in `each'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/registry.rb:48:in `each'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:347:in `default_provider'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:943:in `guess_provider'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:955:in `find_configured_plugins'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:983:in `process_configured_plugins'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:178:in `initialize'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/bin/vagrant:145:in `new'
zepgram: from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/bin/vagrant:145:in `<main>'
zepgram:
==> zepgram: Trigger run failed
==> zepgram: A script exited with an unacceptable exit code 1.
A script exited with an unacceptable exit code 1.
Could you please help me solve this error?
Thanks!
Currently I have a working installation that I can browse products on the front end, use the admin and other user driven things. However I am now trying to replicate my live system and I've overcome many other apt install requirements - but now I've come against an issue with the version of PHP.
config.yaml.example
contains php_version: 'default'
and one might expect that to choose from the one of the supported PHP versions of which 2.3.3 adds support for 7.3. Instead it has installed 7.4.
I assume I can just destroy my current VM and start again with php_version: '7.3'
- however I am not sure why this installed such a PHP version that was known to be incompatible with Magento by default?
[zepgram] GuestAdditions versions on your host (6.1.26) and guest (6.1.16) do not match.
E: Unable to locate package linux-headers-4.9.0-14-amd64
E: Couldn't find any package by glob 'linux-headers-4.9.0-14-amd64'
E: Couldn't find any package by regex 'linux-headers-4.9.0-14-amd64'
First : One BIG Thanks for your solution, it is really fast, specially comparing with one I used before.
I have problems with system time of Debian VM. In parameter file "config.yamI" I enter for time zone: time_zone: 'Europe/Vienna'. All VM set-up goes well only system (Debian) time zone is not equal to Magento (this is correct regarding set-up parameters)
$ timedatectl
Local time: Tue 2019-06-18 21:16:25 GMT
Universal time: Tue 2019-06-18 21:16:25 UTC
RTC time: Tue 2019-06-18 21:16:23
Time zone: Etc/GMT+0 (GMT, +0000)
Network time on: yes
NTP synchronized: no
RTC in local TZ: no
System time is 2 hours less than Magento time, I think I have some other problems in Magento development caused by this fact.
My question: is my timezone situation normal ? How to setup Debian VM with same time zone as is in jaml parameter file (and as is in Magento).
Info about my system:
mac OS Mojove
VirtualBox 5.2.28
Vagrant 2.2.4
Magento 2.3.1 Community + sample data
Thanks in advance for your effort and time to help us, me
Marjan Pečar, Slovenia
When trying to add product i get error (in backend):
TypeError: rawurlencode() expects parameter 1 to be string, int given in /home/vagrant/magento/vendor/laminas/laminas-escaper/src/Escaper.php:246 Stack trace: #0 /home/vagrant/magento/vendor/laminas/laminas-escaper/src/Escaper.php(246): rawurlencode() #1 /home/vagrant/magento/vendor/magento/framework/Escaper.php(286): Laminas\Escaper\Escaper->escapeUrl() #2 /home/vagrant/magento/vendor/magento/framework/Url/RouteParamsResolver.php(115): Magento\Framework\Escaper->encodeUrlParam() #3 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(58): Magento\Framework\Url\RouteParamsResolver->setRouteParams() #4 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Framework\Url\RouteParamsResolver\Interceptor->___callParent() #5 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Framework\Url\RouteParamsResolver\Interceptor->Magento\Framework\Interception\{closure}() #6 /home/vagrant/magento/generated/code/Magento/Framework/Url/RouteParamsResolver/Interceptor.php(23): Magento\Framework\Url\RouteParamsResolver\Interceptor->___callPlugins() #7 /home/vagrant/magento/vendor/magento/framework/Url.php(716): Magento\Framework\Url\RouteParamsResolver\Interceptor->setRouteParams() #8 /home/vagrant/magento/vendor/magento/module-backend/Model/Url.php(189): Magento\Framework\Url->_setRouteParams() #9 /home/vagrant/magento/vendor/magento/framework/Url.php(754): Magento\Backend\Model\Url->_setRouteParams() #10 /home/vagrant/magento/vendor/magento/framework/Url.php(929): Magento\Framework\Url->getRouteUrl() #11 /home/vagrant/magento/vendor/magento/framework/Url.php(873): Magento\Framework\Url->createUrl() #12 /home/vagrant/magento/vendor/magento/module-backend/Model/Url.php(210): Magento\Framework\Url->getUrl() #13 /home/vagrant/magento/vendor/magento/module-catalog/Ui/DataProvider/Product/Form/Modifier/Categories.php(216): Magento\Backend\Model\Url->getUrl() #14 /home/vagrant/magento/vendor/magento/module-catalog/Ui/DataProvider/Product/Form/Modifier/Categories.php(148): Magento\Catalog\Ui\DataProvider\Product\Form\Modifier\Categories->createNewCategoryModal() #15 /home/vagrant/magento/vendor/magento/module-catalog/Ui/DataProvider/Product/Form/ProductDataProvider.php(73): Magento\Catalog\Ui\DataProvider\Product\Form\Modifier\Categories->modifyMeta() #16 /home/vagrant/magento/vendor/magento/framework/View/Element/UiComponentFactory.php(330): Magento\Catalog\Ui\DataProvider\Product\Form\ProductDataProvider->getMeta() #17 /home/vagrant/magento/vendor/magento/framework/View/Element/UiComponentFactory.php(231): Magento\Framework\View\Element\UiComponentFactory->mergeMetadata() #18 /home/vagrant/magento/vendor/magento/framework/View/Layout/Generator/UiComponent.php(140): Magento\Framework\View\Element\UiComponentFactory->create() #19 /home/vagrant/magento/vendor/magento/framework/View/Layout/Generator/UiComponent.php(103): Magento\Framework\View\Layout\Generator\UiComponent->generateComponent() #20 /home/vagrant/magento/vendor/magento/framework/View/Layout/GeneratorPool.php(93): Magento\Framework\View\Layout\Generator\UiComponent->process() #21 /home/vagrant/magento/vendor/magento/framework/View/Layout.php(365): Magento\Framework\View\Layout\GeneratorPool->process() #22 /home/vagrant/magento/generated/code/Magento/Framework/View/Layout/Interceptor.php(68): Magento\Framework\View\Layout->generateElements() #23 /home/vagrant/magento/vendor/magento/framework/View/Layout/Builder.php(129): Magento\Framework\View\Layout\Interceptor->generateElements() #24 /home/vagrant/magento/vendor/magento/framework/View/Page/Builder.php(65): Magento\Framework\View\Layout\Builder->generateLayoutBlocks() #25 /home/vagrant/magento/vendor/magento/framework/View/Layout/Builder.php(65): Magento\Framework\View\Page\Builder->generateLayoutBlocks() #26 /home/vagrant/magento/vendor/magento/framework/View/Layout.php(271): Magento\Framework\View\Layout\Builder->build() #27 /home/vagrant/magento/vendor/magento/framework/View/Layout.php(896): Magento\Framework\View\Layout->build() #28 /home/vagrant/magento/generated/code/Magento/Framework/View/Layout/Interceptor.php(293): Magento\Framework\View\Layout->getBlock() #29 /home/vagrant/magento/vendor/magento/module-backend/Model/View/Result/Page.php(26): Magento\Framework\View\Layout\Interceptor->getBlock() #30 /home/vagrant/magento/generated/code/Magento/Backend/Model/View/Result/Page/Interceptor.php(23): Magento\Backend\Model\View\Result\Page->setActiveMenu() #31 /home/vagrant/magento/vendor/magento/module-catalog/Controller/Adminhtml/Product/NewAction.php(72): Magento\Backend\Model\View\Result\Page\Interceptor->setActiveMenu() #32 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(58): Magento\Catalog\Controller\Adminhtml\Product\NewAction->execute() #33 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Catalog\Controller\Adminhtml\Product\NewAction\Interceptor->___callParent() #34 /home/vagrant/magento/vendor/magento/framework/App/Action/Plugin/ActionFlagNoDispatchPlugin.php(51): Magento\Catalog\Controller\Adminhtml\Product\NewAction\Interceptor->Magento\Framework\Interception\{closure}() #35 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(135): Magento\Framework\App\Action\Plugin\ActionFlagNoDispatchPlugin->aroundExecute() #36 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Catalog\Controller\Adminhtml\Product\NewAction\Interceptor->Magento\Framework\Interception\{closure}() #37 /home/vagrant/magento/generated/code/Magento/Catalog/Controller/Adminhtml/Product/NewAction/Interceptor.php(23): Magento\Catalog\Controller\Adminhtml\Product\NewAction\Interceptor->___callPlugins() #38 /home/vagrant/magento/vendor/magento/framework/App/Action/Action.php(111): Magento\Catalog\Controller\Adminhtml\Product\NewAction\Interceptor->execute() #39 /home/vagrant/magento/vendor/magento/module-backend/App/AbstractAction.php(151): Magento\Framework\App\Action\Action->dispatch() #40 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(58): Magento\Backend\App\AbstractAction->dispatch() #41 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Catalog\Controller\Adminhtml\Product\NewAction\Interceptor->___callParent() #42 /home/vagrant/magento/vendor/magento/module-backend/App/Action/Plugin/Authentication.php(143): Magento\Catalog\Controller\Adminhtml\Product\NewAction\Interceptor->Magento\Framework\Interception\{closure}() #43 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(135): Magento\Backend\App\Action\Plugin\Authentication->aroundDispatch() #44 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Catalog\Controller\Adminhtml\Product\NewAction\Interceptor->Magento\Framework\Interception\{closure}() #45 /home/vagrant/magento/generated/code/Magento/Catalog/Controller/Adminhtml/Product/NewAction/Interceptor.php(32): Magento\Catalog\Controller\Adminhtml\Product\NewAction\Interceptor->___callPlugins() #46 /home/vagrant/magento/vendor/magento/framework/App/FrontController.php(186): Magento\Catalog\Controller\Adminhtml\Product\NewAction\Interceptor->dispatch() #47 /home/vagrant/magento/vendor/magento/framework/App/FrontController.php(118): Magento\Framework\App\FrontController->processRequest() #48 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(58): Magento\Framework\App\FrontController->dispatch() #49 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Framework\App\FrontController\Interceptor->___callParent() #50 /home/vagrant/magento/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}() #51 /home/vagrant/magento/generated/code/Magento/Framework/App/FrontController/Interceptor.php(23): Magento\Framework\App\FrontController\Interceptor->___callPlugins() #52 /home/vagrant/magento/vendor/magento/framework/App/Http.php(116): Magento\Framework\App\FrontController\Interceptor->dispatch() #53 /home/vagrant/magento/generated/code/Magento/Framework/App/Http/Interceptor.php(23): Magento\Framework\App\Http->launch() #54 /home/vagrant/magento/vendor/magento/framework/App/Bootstrap.php(263): Magento\Framework\App\Http\Interceptor->launch() #55 /home/vagrant/magento/pub/index.php(29): Magento\Framework\App\Bootstrap->run() #56 {main}
Hello,
I am trying to install the VM. The vagrant up commands runs for some time and then I get these error messages at the end:
....
zepgram: Package guzzlehttp/ringphp is abandoned, you should avoid using it. No replacement was suggested.
zepgram: Package zendframework/zend-json is abandoned, you should avoid using it. Use laminas/laminas-json instead.
zepgram: Package zendframework/zend-view is abandoned, you should avoid using it. Use laminas/laminas-view instead.
zepgram: Package zendframework/zend-text is abandoned, you should avoid using it. Use laminas/laminas-text instead.
zepgram: Package zendframework/zend-server is abandoned, you should avoid using it. Use laminas/laminas-server instead.
zepgram: Package zendframework/zend-soap is abandoned, you should avoid using it. Use laminas/laminas-soap instead.
zepgram: Package zendframework/zend-serializer is abandoned, you should avoid using it. Use laminas/laminas-serializer instead.
zepgram: Package zendframework/zend-config is abandoned, you should avoid using it. Use laminas/laminas-config instead.
zepgram: Package zendframework/zend-modulemanager is abandoned, you should avoid using it. Use laminas/laminas-modulemanager instead.
zepgram: Package zendframework/zend-log is abandoned, you should avoid using it. Use laminas/laminas-log instead.
zepgram: Package zendframework/zend-i18n is abandoned, you should avoid using it. Use laminas/laminas-i18n instead.
zepgram: Package zendframework/zend-feed is abandoned, you should avoid using it. Use laminas/laminas-feed instead.
zepgram: Package phpunit/phpunit-mock-objects is abandoned, you should avoid using it. No replacement was suggested.
zepgram: Package facebook/webdriver is abandoned, you should avoid using it. Use php-webdriver/webdriver instead.
zepgram:
zepgram: Installation failed, reverting ./composer.json to its original content.
zepgram:
zepgram: [Composer\Repository\InvalidRepositoryException]
zepgram: Invalid repository data in /home/vagrant/magento/vendor/composer/installed.json, packages could not be loaded: [Seld\JsonLint\ParsingException] "/home/vagrant/magento/vendor/composer/installed.json" does not contain valid JSON
zepgram: Parse error on line 1:
zepgram:
zepgram: ^
zepgram: Expected one of: 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '['
zepgram:
zepgram: require [--dev] [--prefer-source] [--prefer-dist] [--fixed] [--no-progress] [--no-suggest] [--no-update] [--no-scripts] [--update-no-dev] [--update-with-dependencies] [--update-with-all-dependencies] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--] [<packages>]...
zepgram:
zepgram: [Composer\Repository\InvalidRepositoryException]
zepgram: Invalid repository data in /home/vagrant/magento/vendor/composer/installed.json, packages could not be loaded: [Seld\JsonLint\ParsingException] "/home/vagrant/magento/vendor/composer/installed.json" does not contain valid JSON
zepgram: Parse error on line 1:
zepgram:
zepgram: ^
zepgram: Expected one of: 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '['
zepgram:
zepgram: chmod:
zepgram: cannot access '/home/vagrant/magento/bin/magento'
zepgram: : No such file or directory
zepgram: sudo
zepgram: :
zepgram: /home/vagrant/magento/bin/magento: command not found
zepgram: sudo
zepgram: :
zepgram: /home/vagrant/magento/bin/magento: command not found
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
Any ideas?
It seems that grunt isn't installed.
Maybe due to debian strch version 9, in provision/010-system.packages.sh
Just change
# Grunt
curl -sL https://deb.nodesource.com/setup_8.x | -E bash -
apt-get install -y nodejs
npm install -g grunt-cli
to
# Grunt
curl -sL https://deb.nodesource.com/setup_10.x | -E bash -
sudo apt-get install -y nodejs
npm install -g grunt-cli
After installation, when i enter: vagrant ssh. Then it asks for:
[email protected]'s password: ?
Kindly help. Thank you.
Hi,
I'm struggling with this virtual machine quite some time already. First, I modified config.yaml to my own needs (M.2.1.13) and made a change to enforce PHP7.0 and had lots of no-joy.
To eliminate my own potential mistakes, I now took your original again. Changes made: copied ssh keys to Directory ssh & uncommenting # v.gui=true
Still fails, last lines of vagrant report is:
` zepgram: create-project [-s|--stability STABILITY] [--prefer-source] [--prefer-dist] [--repository REPOSITORY] [--repository-url REPOSITORY-URL] [--dev] [--no-dev] [--no-custom-installers] [--no-scripts] [--no-progress] [--no-secure-http] [--keep-vcs] [--remove-vcs] [--no-install] [--ignore-platform-reqs] [--] [] [] []
zepgram: 1/2: http://repo.packagist.org/p/provider-latest$171f3560ee0f99757671c1f039c524673ab3e64a89c76599852053047741ce1d.json
zepgram: 2/2: http://repo.packagist.org/p/provider-2019-01$1f3f3a6254adeff2c22659a929fa84b42be754809f216a81d82f524ce761e370.json
zepgram: Finished: success: 2, skipped: 0, failure: 0, total: 2
zepgram: 1/2: http://repo.packagist.org/p/provider-latest$171f3560ee0f99757671c1f039c524673ab3e64a89c76599852053047741ce1d.json
zepgram: 2/2: http://repo.packagist.org/p/provider-2019-01$1f3f3a6254adeff2c22659a929fa84b42be754809f216a81d82f524ce761e370.json
zepgram: Finished: success: 2, skipped: 0, failure: 0, total: 2
zepgram: 1/2: http://repo.packagist.org/p/provider-latest$171f3560ee0f99757671c1f039c524673ab3e64a89c76599852053047741ce1d.json
zepgram: 2/2: http://repo.packagist.org/p/provider-2019-01$1f3f3a6254adeff2c22659a929fa84b42be754809f216a81d82f524ce761e370.json
zepgram: Finished: success: 2, skipped: 0, failure: 0, total: 2
zepgram:
zepgram: [InvalidArgumentException]
zepgram: Could not find a matching version of package magento/module-bundle-sample-data. Check the package spelling, your version constraint and that the package is available in a stability which matches your minimum-stability (stable).
zepgram:
zepgram:
zepgram: require [--dev] [--prefer-source] [--prefer-dist] [--no-progress] [--no-suggest] [--no-update] [--no-scripts] [--update-no-dev] [--update-with-dependencies] [--update-with-all-dependencies] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--] []…
zepgram: Loading composer repositories with package Information
zepgram: Updating dependencies (including require-dev)
zepgram: Nothing to install or update
zepgram: Generating autoload files
zepgram: sudo
zepgram:
zepgram: /srv/magento/bin/magento: command not found
zepgram: sudo
zepgram:
zepgram: /srv/magento/bin/magento: command not found
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.`
Hello,
I am using Ubuntu 18.04 with PHP 7.4 and trying to use this repo to install Magento 2.4.
I seem to get an error when trying to authenticate with the magento repo using composer:
However, I have entered my magento credentials in config.yaml and the magento credentials I am using work for accessing www.magentocommerce.com/products/downloads/info/help since it does not give me a 401 Unauthorized error:
Any suggestions?
Here is my config.yaml (I also had problems with it getting stuck on NFS mount step so I am trying rsync instead):
vmconf:
machine_name: 'Vagrant Magento 2'
network_ip: '192.168.200.50'
host_name: 'zepgram'
memory: '4096'
cpus: '1'
mount: 'rsync'
path: 'root'
provision: 'all'
composer:
username: 'MAG#HERE'
password: 'CORRECTKEYHERE'
git:
name: 'John Doe'
email: '[email protected]'
host: 'github.com'
repository: 'ssh://[email protected]:project-name.git'
magento:
url: 'dev.magento.com'
source: 'composer'
edition: 'community'
version: '2.4.0'
php_version: 'default'
sample: 'true'
mode: 'developer'
currency: 'USD'
language: 'en_US'
time_zone: 'America/New_York'
crypt_key: ''
Is there a way to clone a repo from bitbucket? It tried by changing the credentials but I'm getting an error with vagrant up?
ssh: Could not resolve hostname bitbucket.org:
Hi @zepgram I installed this project and set it up with an existing project from my repo. Now this project is already working. Now I redownloaded your project and reinstalled the magento 2.3.1 version. At first it gave me an error saying Cannot find magento.store_website
which I think is just correct? Since I'm loading an existing project and the Magento DB is not created since I didn't go to the whole db/website installation process. So I uploaded my own DB dump from the created MariaDB connection. Now I did a vagrant reload --provision then visited the Admin. Upon visiting it I got an error saying the website is in Maintenance mode so I run bin/magento maintenance:disable
then revisit the site again. Now it says the Application is not installed. So whenever I visit the site it redirects me to the Setup Page
. Any idea regarding this?
Edit: Upon digging some more it seems that even if I set my config.yaml to pull from existing project it's trying to install Magento as a clean state? It's installing the database schema for the installation of installDataFixtures. And since it's installing from existing project there are no Database when doing vagrant reload --provision since somehow the database and all tables are being deleted. Now when I manually upload the DB dump and access the db that's when I get the mode is set to maintenance mode (which is why I needed to disable it every now and then). Below is the scripts that causes the issue
FIle: approot/setup/src/Magento/Setup/Model/Installer.php
Line: 328
Function:
public function install($request)
{
$script[] = ['File permissions check...', 'checkInstallationFilePermissions', []];
$script[] = ['Required extensions check...', 'checkExtensions', []];
$script[] = ['Enabling Maintenance Mode...', 'setMaintenanceMode', [1]];
$script[] = ['Installing deployment configuration...', 'installDeploymentConfig', [$request]];
if (!empty($request[InstallCommand::INPUT_KEY_CLEANUP_DB])) {
$script[] = ['Cleaning up database...', 'cleanupDb', []];
}
$script[] = ['Installing database schema:', 'installSchema', [$request]];
$script[] = ['Installing user configuration...', 'installUserConfig', [$request]];
$script[] = ['Enabling caches:', 'enableCaches', []];
$script[] = ['Installing data...', 'installDataFixtures', [$request]];
if (!empty($request[InstallCommand::INPUT_KEY_SALES_ORDER_INCREMENT_PREFIX])) {
$script[] = [
'Creating sales order increment prefix...',
'installOrderIncrementPrefix',
[$request[InstallCommand::INPUT_KEY_SALES_ORDER_INCREMENT_PREFIX]],
];
}
if ($this->isAdminDataSet($request)) {
$script[] = ['Installing admin user...', 'installAdminUser', [$request]];
}
if (!$this->isDryRun($request)) {
$script[] = ['Caches clearing:', 'cleanCaches', [$request]];
}
$script[] = ['Disabling Maintenance Mode:', 'setMaintenanceMode', [0]];
$script[] = ['Post installation file permissions check...', 'checkApplicationFilePermissions', []];
$script[] = ['Write installation date...', 'writeInstallationDate', []];
$estimatedModules = $this->createModulesConfig($request, true);
$total = count($script) + 4 * count(array_filter($estimatedModules));
$this->progress = new Installer\Progress($total, 0);
$this->log->log('Starting Magento installation:');
foreach ($script as $item) {
list($message, $method, $params) = $item;
$this->log->log($message);
call_user_func_array([$this, $method], $params);
$this->logProgress();
}
$this->log->logSuccess('Magento installation complete.');
$this->log->logSuccess(
'Magento Admin URI: /'
. $this->deploymentConfig->get(BackendConfigOptionsList::CONFIG_PATH_BACKEND_FRONTNAME)
);
if ($this->progress->getCurrent() != $this->progress->getTotal()) {
throw new \LogicException('Installation progress did not finish properly.');
}
if ($this->sampleDataState->hasError()) {
$this->log->log('Sample Data is installed with errors. See log file for details');
}
}
Is this the correct process? Doing a DB dump? or probably offer the script to upload an existing DB dump perhaps? so that if the installer check for the dump it won't fail this there are already an existing db.
Or maybe you have a solution for my issue? Would really appreciate your help on this
While is vagrant up i have this warning :
dev.xxxxxx.com: chown: changing ownership of '/home/vagrant/magento/vendor/magento/magento2-base/dev/tests/api-functional/_files/Magento/TestModuleJoinDirectives/etc/acl.xml': Operation not permitted
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.