[2.2.0-RC1.1] Generate static content command still requires DB connection

[jahvi]

Based on the technical details for the upcoming Magento 2.2 version it seems like you can generate static content without access to the DB, however it still seems to be trying to connect to the DB in my case.

Preconditions

1. Magento 2.2 RC1.1 (3cfa32b)
2. PHP 7.0.19

Steps to reproduce

1. Clone latest develop branch
2. Install Magento
3. Run php bin/magento app:config:dump
4. Rename env.php file to env2.php
5. Run php bin/magento setup:static-content:deploy -l en_US -t Magento/blank -f

Expected result

1. Static content should be deployed for the blank theme under en_US locale.

Actual result

Deploy using quick strategy


  [DomainException]
  Default website is not defined


setup:static-content:deploy [-f|--force] [-s|--strategy [STRATEGY]] [-a|--area [AREA]] [--exclude-area [EXCLUDE-AREA]] [-t|--theme [THEME]] [--exclude-theme [EXCLUDE-THEME]] [-l|--language [LANGUAGE]] [--exclude-language [EXCLUDE-LANGUAGE]] [-j|--jobs [JOBS]] [--symlink-locale] [--content-version CONTENT-VERSION] [--refresh-content-version-only] [--no-javascript] [--no-css] [--no-less] [--no-images] [--no-fonts] [--no-html] [--no-misc] [--no-html-minify] [--] [<languages>]...

If you rename the env.php file back it works fine. Am I missing something here?

I think I need to set the settings that Magento is trying to get from the DB in the env.php file of my build machine so it doesn't need to query the database but I'm not sure how.

[ihor-sviziev]

Take a look on deployment pipeline docs: http://devdocs.magento.com/guides/v2.2/config-guide/deployment/pipeline/
It looks like you should have config.php to deploy static content.

[jahvi]

I had a look at the docs (as I link in the original issue) but they don't mention anything I haven't tried unfortunately, I do have the default config.php file you get after installing Magento but I perhaps I need to tweak it for building?

[misha-kotov]

@jahvi Before you run static content deploy, dump your configuration to file by app:config:dump. This will write additional config to config.php file that is needed to generate static view files.

[jahvi]

@misha-kotov Thanks, I ran the app:config:dump command and my config.php file got updated, however I'm still getting the Default website is not defined error when I try to generate static assets.

[misha-kotov]

Do you have a website defined in Stores > Settings > All Stores?

[jahvi]

Yes, this is how it looks in my config.php file:

<?php
return array (
  ...
  'scopes' =>
  array (
    'websites' =>
    array (
      'admin' =>
      array (
        'website_id' => '0',
        'code' => 'admin',
        'name' => 'Admin',
        'sort_order' => '0',
        'default_group_id' => '0',
        'is_default' => '0',
      ),
      'base' =>
      array (
        'website_id' => '1',
        'code' => 'base',
        'name' => 'Main Website',
        'sort_order' => '0',
        'default_group_id' => '1',
        'is_default' => '1',
      ),
    ),
    'groups' =>
    array (
      0 =>
      array (
        'group_id' => '0',
        'website_id' => '0',
        'code' => 'default',
        'name' => 'Default',
        'root_category_id' => '0',
        'default_store_id' => '0',
      ),
      1 =>
      array (
        'group_id' => '1',
        'website_id' => '1',
        'code' => 'main_website_store',
        'name' => 'Main Website Store',
        'root_category_id' => '2',
        'default_store_id' => '1',
      ),
    ),
    'stores' =>
    array (
      'admin' =>
      array (
        'store_id' => '0',
        'code' => 'admin',
        'website_id' => '0',
        'group_id' => '0',
        'name' => 'Admin',
        'sort_order' => '0',
        'is_active' => '1',
      ),
      'default' =>
      array (
        'store_id' => '1',
        'code' => 'default',
        'website_id' => '1',
        'group_id' => '1',
        'name' => 'Default Store View',
        'sort_order' => '0',
        'is_active' => '1',
      ),
    ),
  ),
  ...
);

[misha-kotov]

We're looking into this issue.

[tjwiebell]

@jahvi - Bug confirmed and internal issue MAGETWO-70318 has been created. We'll let you know if we have any additional questions.

[mslabko]

Hi @jahvi , the issue has been fixed and will be delivered in one of the nearest releases. Thank you!