Sample data for CE about magento2-vagrant-for-developers HOT 10 CLOSED

@Szaamaan can you please post here your config.yaml content (repository_url and magento sections)?

from magento2-vagrant-for-developers.

@paliarush Like I wrote, I'm using the stock config basically:

repository_url:
  # [To apply changes: init-project -fc]
  # [email protected]:magento/magento2ce.git OR custom one
  ce: "[email protected]:magento/magento2.git"
  # [email protected]:magento/magento2ee.git OR custom one
  ee: ""
  # can be replaced with custom repository
  ce_sample_data: "[email protected]:magento/magento2-sample-data.git"
  # [email protected]:magento/magento2-sample-data-ee.git OR custom one
ee_sample_data: ""

The only changes I've made to the config are:

• in guest I've increased memory
• in magento I've set install_sample_data to 1 and changed the host name

from magento2-vagrant-for-developers.

Config looks good.

Have you tried to run bash ./init_project.sh -fc? Note that this command will remove your current code base and box itself, then will recreate everything from scratch.

There are 2 ways to install sample data: via composer or via linking git repositories. Here we use second approach. So don't try m-bin-magento sampledata:deploy. BTW, there was a typo in your command bash m-bin-magento sample:deploy, should be sampledata:deploy.

from magento2-vagrant-for-developers.

@paliarush Yes. I've tried that. Again, it seems the sample data is somehow incompatible with the dev version of Magento...

from magento2-vagrant-for-developers.

Just set up new instance of vagrant project from scratch using the following settings and sample data was successfully installed:

repository_url:
  ce: "[email protected]:magento/magento2.git"
  ee: ""
  ce_sample_data: "[email protected]:magento/magento2-sample-data.git"
  ee_sample_data: ""
magento:
  # [To apply changes: m-switch-to-ce -f OR m-switch-to-ee -f]
  install_sample_data: 1

BTW specified sample data repository is kept in sync with develop branch of Magento, so this should not be a problem.

My host is OSX, which one do you have? Unfortunately I don't have access to Windows host at the moment to test it.

Will leave it open, maybe someone also has the same problem. Thanks for reporting this.

from magento2-vagrant-for-developers.

In that case it might be something with the script running on a Windows host. Again, sample data is never installed, despite the correct settings in config.yaml.

EDIT:
Excuse my ignorance, but perhaps I'm missing some step?

From my understanding - running the config you posted should result in a working Magento installation already populated with sample data (visible right on the main page)? If not, then is there another thing required?

If no other commands or changes are needed then I have a feeling it might be the symlinks on Windows not working the same way they might be under other OSes.

from magento2-vagrant-for-developers.

@Szaamaan just looked at init_project.sh and found old comment related to linking EE (the same is valid for sample data linking):

Automatic switch to EE during project initialization cannot be supported on Windows

So on Windows you will not get EE and Sample data installed just by running init_project.sh.
You need to perform one more step after CE with no sample data is successfully installed. Run m-switch-to-ce -f, then you should see prompt:

Wait while Magento2 code is uploaded in PhpStorm and press any key to continue...

Basically you need to make sure that after symlinks were created on your host, all Sample data files are uploaded to the guest. Current recommended way to do this is using PhpStorm deployment feature (should be configured for you by init_project.sh), however you can use any other sync method (e.g. rsync).

After you hit any button to continue installation, Magento with sample data should be installed.

from magento2-vagrant-for-developers.

Hi,

I'm having the same issue on OSX 10.11.6.

One thing I noticed is when doing a ls of $MAGENTO_ROOT/dev/tools is that the symlink seems to be an invalid one. Could it be due to the case sensitivity of the file paths (users vs Users)?

from magento2-vagrant-for-developers.

@jasonheecs since OSX is case insensitive and Ubuntu is case sensitive, it can be a problem. Please read item 9 in https://github.com/paliarush/magento2-vagrant-for-developers#faq

I recommend to do init_project.sh -fc in this case (will pull codebase again and re-create box based on your current config.yaml).

from magento2-vagrant-for-developers.

For some reason Windows Git Bash doesn't always show the message "Wait while ...". It just stops without any message on screen. I have all debugging options set. Anyhow log file m-switch-to-ce.log shows the message when execution stops.
Proposed solution works so just copy/deploy manually sample data from host to guest and continue installation.

from magento2-vagrant-for-developers.