• Twig cache invalidation, cache invalidation in general
  • Handling CSS and JS aggregates; at the moment I'm achieving this with object storage (see below) paired with AdvAgg module and hook_advagg_asset_path_alter
  • File storage; e.g., using object storage and a filesystem abstraction layer such as Flysystem
  • Reverse proxies and load balancing
  • Allow private file system to be a remote object storage
  • ...

Comments

anavarre’s picture

Issue tags: +scalability
Wim Leers’s picture

almaudoh’s picture

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

bradjones1’s picture

Issue summary: View changes

Being bold and editing the description with some points that need covered

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

geerlingguy’s picture

Issue tags: +kubernetes

Adding tag for Kubernetes/12fa tracking purposes. The issues for multiple web heads and Kubernetes are not always the same, but are definitely very similar.

T-lo’s picture

I'd really appreciate even a slight expansion on the Handling CSS and JS aggregates point. In D7 advagg used to build these on 404 but it seems not to in D8 so I'm currently stuck trying to get them into flysystem.

bradjones1’s picture

An approach to CSS/JS with object storage: Flysystem is great and I think there is even some thought being given to it going into core...but it does require a little tweaking. Specifically, if you are also using a CDN (which I think is a bit of a must to offload regular filesystem operations from the server, since it's all piped through in userspace) you can't necessarily put your CSS there, due to some relative path weirdness.

$schemes['gcs'] = [
  'driver' => 'gcs',
  'config' => [
    'bucket' => 'bucketname',
    'keyFilePath' => '/secrets/serviceaccount.json',
    'projectId' => 'projectId',
    '_localConfig' => [
      // Use self-referential URL for CSS/JS.
      'uri' => getenv('DRUSH_OPTIONS_URI') . '/_flysystem/gcs',
    ],
  ],
  'name' => 'GCS',
  'cache' => TRUE,
  'serve_js' => TRUE,
  'serve_css' => TRUE,
];

I did recently contribute some changes to flysystem_gcs to enable the above configuration; not sure what driver you're using. There's lots to be done in this space. I'd recommend hooking up with the https://github.com/drud/sig-drupal group which is kinda-sorta Kubernetes focused but is really just a group of cloud-native people. There's surprisingly little public work going on in this space, potentially due to the fact many big sites are configured in a proprietary configuration and/or utilize a PaaS, but there's a growing group of us who are looking to demystify. (And to be fair the sig includes a number of progressive organizations like Amazee, who run platforms.)

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

bradjones1’s picture

Title: Create comprehensive documentation for Drupal 8 on multiple web heads » Create comprehensive documentation for running Drupal in a "cloud-native" or 12-Factor App model
Version: 8.9.x-dev » 9.3.x-dev
Priority: Major » Normal
mglaman’s picture

Issue summary: View changes

Adding note after I had an error with Commerce Invoice fail to install due to private file path not being set

[error]  Unable to install module 'commerce_invoice' due to unmet requirement(s):
  - Commerce Invoice requires the private file system path to be configured.

It'd be great to keep private:// but have it map to an object storage

bradjones1’s picture

Or better yet, since there's a lot of logic baked into the BC layer around "private" per se, allow you to set which scheme serves as default private storage.

mglaman’s picture

Per #18 maybe that should be the focus. Let's stop defining more stream wrappers but identify what should serve as the public or private wrapper, while still allowing new ones.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

bradjones1’s picture

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.