@lando/drupal 0.12.0 → 1.0.0

package/node_modules/@lando/php/PRIVACY.md

@@ -0,0 +1,169 @@
+# Privacy Policy
+
+Effective date: November 26, 2019
+
+Kalabox Inc DBA Tandem ("Tandem", "us", "we", or "our") operates the Lando software (hereinafter referred to as the "Software").
+
+This page informs you of our policies regarding the collection, use and disclosure of personal data when you use our Software and the choices you have associated with that data.
+
+The Software automatically communicates with Tandem to send error reports and collect usage data so we may improve the Software and fix critical bugs.
+
+We use your data to provide and improve the Software. By using the Software, you agree to the collection and use of information in accordance with this policy. Unless otherwise defined in this Privacy Policy, the terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, accessible at https://raw.githubusercontent.com/lando/lando/master/TERMS.md
+
+For a more human readable explanation of this, check out: https://docs.lando.dev/help/data.html
+
+## Definitions
+
+### Software
+
+Software is Lando operated by Tandem
+
+### Personal Data
+
+Personal Data means data about a living individual who can be identified from those data (or from those and other information either in our possession or likely to come into our possession).
+
+### Usage Data
+
+Usage Data is data collected automatically by the use of the Software.
+
+### Crash Data
+
+Crash Data is data collected automatically by the use of the Software when it crashes or errors.
+
+### Data Controller
+
+Data Controller means the natural or legal person who (either alone or jointly or in common with other persons) determines the purposes for which and the manner in which any personal information are, or are to be, processed.
+
+For the purpose of this Privacy Policy, we are a Data Controller of your Personal Data.
+
+### Data Processors (or Software Providers)
+
+Data Processor (or Software Provider) means any natural or legal person who processes the data on behalf of the Data Controller.
+
+We may use the Softwares of various Software Providers in order to process your data more effectively.
+
+### Data Subject (or User)
+
+Data Subject is any living individual who is using our Software and is the subject of Personal Data.
+
+## Information Collection and Use
+
+We collect several different types of information for various purposes to provide and improve our Software to you.
+
+### Types of Data Collected
+
+#### Usage Data
+
+Usage data does not contain any Personal Data such as an IP Address or Email. However, each Lando instance is associated with an identification key. The Data Subject themselves is the only person who would be able to use this identification key to identify relevant Usage Data as theirs.
+
+You may opt out of sending the usage data and error reports by following instructions provided in relevant Software documentation.
+
+#### Crash Data
+
+Crash Data will only be sent to Tandem if the user opts in and gives us permission to do so. We have tried our best to pseudonymize Crash Data, but recognize that some path names and other information that we collect may inadvertently include Personal Data, including but not limited to usernames and site names.
+
+View a Lando log file to see a sample of what we collect.
+https://docs.lando.dev/help/data.html
+
+## Use of Data
+
+Tandem uses the collected data for various purposes:
+
+* To help prioritize bug fixes and features to the Software
+* To assist in the fixing of critical issues to the Software
+* To detect, prevent and address technical issues
+* To provide customer support
+* To gather analysis or valuable information so that we can improve our Service
+* To monitor the usage of our Service
+
+### Legal Basis for Processing Personal Data under the General Data Protection Regulation (GDPR)
+
+If you are from the European Economic Area (EEA), Tandem's legal basis for collecting and using the personal information described in this Privacy Policy depends on the Personal Data we collect and the specific context in which we collect it.
+
+Tandem's may process your Personal Data because:
+
+* You have given us permission to do so
+* The processing is in our legitimate interests and it is not overridden by your rights
+* To comply with the law
+
+## Retention of Data
+
+Tandem will retain your Personal Data only for as long as is necessary for the purposes set out in this Privacy Policy. We will retain and use your Personal Data to the extent necessary to comply with our legal obligations (for example, if we are required to retain your data to comply with applicable laws), resolve disputes and enforce our legal agreements and policies.
+
+Tandem will also retain Usage Data for internal analysis purposes. Usage Data is generally retained for a shorter period of time, except when this data is used to strengthen the security or to improve the functionality of our Software, or we are legally obligated to retain this data for longer periods.
+
+## Transfer of Data
+
+Your information, including Personal Data, may be transferred to - and maintained on - computers located outside of your state, province, country or other governmental jurisdiction where the data protection laws may differ from those of your jurisdiction.
+
+If you are located outside United States and choose to provide information to us, please note that we transfer the data, including Personal Data, to United States and process it there.
+
+Your consent to this Privacy Policy followed by your submission of such information represents your agreement to that transfer.
+
+Tandem will take all the steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy and no transfer of your Personal Data will take place to an organisation or a country unless there are adequate controls in place including the security of your data and other personal information.
+
+## Disclosure of Data
+
+### Disclosure for Law Enforcement
+
+Under certain circumstances, Tandem may be required to disclose your Personal Data if required to do so by law or in response to valid requests by public authorities (e.g. a court or a government agency).
+
+### Legal Requirements
+
+Tandem may disclose your Personal Data in the good faith belief that such action is necessary to:
+
+* To comply with a legal obligation
+* To protect and defend the rights or property of Tandem
+* To prevent or investigate possible wrongdoing in connection with the Software
+* To protect the personal safety of users of the Software or the public
+* To protect against legal liability
+
+## Security of Data
+
+The security of your data is important to us but remember that no method of transmission over the Internet or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.
+
+## Your Data Protection Rights under the General Data Protection Regulation (GDPR)
+
+If you are a resident of the European Economic Area (EEA), you have certain data protection rights. Tandem aims to take reasonable steps to allow you to correct, amend, delete or limit the use of your Personal Data.
+
+If you wish to be informed about what Personal Data we hold about you and if you want it to be removed from our systems, please contact us.
+
+In certain circumstances, you have the following data protection rights:
+
+* The right to access, update or delete the information we have on you. Whenever made possible, you can access, update or request deletion of your Personal Data directly within your account settings section. If you are unable to perform these actions yourself, please contact us to assist you.
+* The right of rectification. You have the right to have your information rectified if that information is inaccurate or incomplete.
+* The right to object. You have the right to object to our processing of your Personal Data.
+* The right of restriction. You have the right to request that we restrict the processing of your personal information.
+* The right to data portability. You have the right to be provided with a copy of the information we have on you in a structured, machine-readable and commonly used format.
+* The right to withdraw consent. You also have the right to withdraw your consent at any time where Tandem relied on your consent to process your personal information.
+
+Please note that we may ask you to verify your identity before responding to such requests.
+
+You have the right to complain to a Data Protection Authority about our collection and use of your Personal Data. For more information, please contact your local data protection authority in the European Economic Area (EEA).
+
+## Software Providers
+
+Tandem utilizes services from Bugsnag Inc. and Qbox, Inc. to store and process data from the Software and has obtained DPAs with both entities for this purpose.
+
+These third parties have access to your Personal Data only to perform these tasks on our behalf and are obligated not to disclose or use it for any other purpose.
+
+## Links to Other Sites
+
+Our Software may contain links to other sites that are not operated by us. If you click a third party link, you will be directed to that third party's site. We strongly advise you to review the Privacy Policy of every site you visit.
+
+We have no control over and assume no responsibility for the content, privacy policies or practices of any third party sites or Softwares.
+
+## Changes to This Privacy Policy
+
+We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.
+
+We will let you know via email and/or a prominent notice on our Software, prior to the change becoming effective and update the "effective date" at the top of this Privacy Policy.
+
+You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.
+
+## Contact Us
+
+If you have any questions about this Privacy Policy, please contact us:
+
+By email: alec@lando.dev
+By visiting this page on our website: https://lando.dev/privacy

package/node_modules/@lando/php/README.md

@@ -0,0 +1,53 @@
+# PHP Lando Plugin
+
+This is the _official_ [Lando](https://lando.dev) plugin for [PHP](https://php.net). When installed it...
+
+* Allows users to run various `php` versions
+* Serves applications over `nginx` or `apache`
+* Runs in `cli` mode
+* Comes with easy `composer` support
+
+Of course, once a user is running their PHP project with Lando they can take advantage of [all the other awesome development features](https://docs.lando.dev) Lando provides.
+
+## Basic Usage
+
+Add a `php` service to your Landofile
+
+```yaml
+services:
+  myservice:
+    type: php:8.1
+    via: nginx
+    webroot: www
+```
+
+For more info you should check out the [docs](https://docs.lando.dev/php):
+
+* [Getting Started](https://docs.lando.dev/php/)
+* [Configuration](https://docs.lando.dev/php/config.html)
+* [Guides](https://docs.lando.dev/php/accessing-logs.html)
+* [Examples](https://github.com/lando/php/tree/main/examples)
+* [Development](https://docs.lando.dev/php/development.html)
+
+## Issues, Questions and Support
+
+If you have a question or would like some community support we recommend you [join us on Slack](https://launchpass.com/devwithlando).
+
+If you'd like to report a bug or submit a feature request then please [use the issue queue](https://github.com/lando/php/issues/new/choose) in this repo.
+
+## Changelog
+
+We try to log all changes big and small in both [THE CHANGELOG](https://github.com/lando/php/blob/main/CHANGELOG.md) and the [release notes](https://github.com/lando/php/releases).
+
+## Contributors
+
+<a href="https://github.com/lando/php/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=lando/php" />
+</a>
+
+Made with [contributors-img](https://contrib.rocks).
+
+## Other Selected Resources
+
+* [LICENSE](https://github.com/lando/php/blob/main/LICENSE.md)
+* [The best professional advice ever](https://www.youtube.com/watch?v=tkBVDh7my9Q)

package/node_modules/@lando/php/builders/php-nginx.js

@@ -0,0 +1,15 @@
+'use strict';
+
+const _ = require('lodash');
+const LandoNginx = require('@lando/nginx/builders/nginx.js');
+
+// Builder
+module.exports = {
+  name: 'php-nginx',
+  parent: '_webserver',
+  builder: (parent, config) => class PhpNginx extends LandoNginx.builder(parent, LandoNginx.config) {
+    constructor(id, options = {}) {
+      super(id, options, {services: _.set({}, options.name)});
+    };
+  },
+};

package/node_modules/@lando/php/builders/php.js

@@ -0,0 +1,222 @@
+'use strict';
+
+// Modules
+const _ = require('lodash');
+const path = require('path');
+const semver = require('semver');
+const addBuildStep = require('./../utils/add-build-step');
+/*
+ * Helper to get nginx config
+ */
+const nginxConfig = options => ({
+  app: options.app,
+  config: _.merge({}, {
+    vhosts: `${options.confDest}/${options.defaultFiles.vhosts}`,
+  }, options.config),
+  confDest: path.resolve(options.confDest, '..', 'nginx'),
+  info: {managed: true},
+  home: options.home,
+  name: `${options.name}_nginx`,
+  overrides: require('../utils/clone-overrides')(options.overrides),
+  project: options.project,
+  root: options.root,
+  ssl: options.nginxSsl,
+  type: options.nginxServiceType,
+  userConfRoot: options.userConfRoot,
+  webroot: options.webroot,
+  version: options.via.split(':')[1],
+});
+
+const xdebugConfig = host => ([
+  `client_host=${host}`,
+  'discover_client_host=1',
+ 'log=/tmp/xdebug.log',
+ 'remote_enable=true',
+  `remote_host=${host}`,
+].join(' '));
+
+/*
+ * Helper to build a package string
+ */
+const pkger = (pkg, version) => (!_.isEmpty(version)) ? `${pkg}:${version}` : pkg;
+
+/*
+ * Helper to parse apache config
+ */
+const parseApache = options => {
+  if (options.ssl) options.defaultFiles.vhosts = 'default-ssl.conf';
+  options.volumes.push(`${options.confDest}/${options.defaultFiles.vhosts}:${options.remoteFiles.vhosts}`);
+  if (options.version === '5.3') options.environment.APACHE_LOG_DIR = '/var/log';
+  return options;
+};
+
+/*
+ * Helper to parse cli config
+ */
+const parseCli = options => {
+  options.command = [_.get(options, 'command', 'tail -f /dev/null')];
+  return options;
+};
+
+/*
+ * Helper to parse nginx config
+ */
+const parseNginx = options => {
+  options.command = (process.platform !== 'win32') ? ['php-fpm'] : ['php-fpm -R'];
+  options.phpServer = 'fpm';
+  options.remoteFiles.vhosts = '/opt/bitnami/nginx/conf/lando.conf';
+  options.defaultFiles.vhosts = (options.ssl) ? 'default-ssl.conf.tpl' : 'default.conf.tpl';
+  options.nginxSsl = options.ssl;
+  options.ssl = false;
+  if (process.platform === 'win32') {
+    options.volumes.push(`${options.confDest}/zz-lando.conf:/usr/local/etc/php-fpm.d/zz-lando.conf`);
+  }
+  options.remoteFiles.pool = '/usr/local/etc/php-fpm.d/zz-lando.conf';
+  return options;
+};
+
+/*
+ * Helper to parse php config
+ */
+const parseConfig = options => {
+  switch (options.via.split(':')[0]) {
+    case 'apache': return parseApache(options);
+    case 'cli': return parseCli(options);
+    case 'nginx': return parseNginx(options);
+  }
+};
+
+// Builder
+module.exports = {
+  name: 'php',
+  config: {
+    version: '7.4',
+    supported: ['8.2', '8.1', '8.0', '7.4', '7.3', '7.2', '7.1', '7.0', '5.6', '5.5', '5.4', '5.3'],
+    legacy: ['7.2', '7.1', '7.0', '5.6', '5.5', '5.4', '5.3'],
+    gen2: ['5.5', '5.4', '5.3'],
+    gen3: ['7.2', '7.1', '7.0', '5.6'],
+    path: [
+      '/app/vendor/bin',
+      '/app/bin',
+      '/usr/local/sbin',
+      '/usr/local/bin',
+      '/usr/sbin',
+      '/usr/bin',
+      '/sbin',
+      '/bin',
+      '/var/www/.composer/vendor/bin',
+      '/helpers',
+    ],
+    confSrc: path.resolve(__dirname, '..', 'config'),
+    command: ['sh -c \'a2enmod rewrite && apache2-foreground\''],
+    composer_version: '2.2.18',
+    phpServer: 'apache',
+    defaultFiles: {
+      _php: 'php.ini',
+      vhosts: 'default.conf',
+      // server: @TODO? DO THE PEOPLE DEMAND IT?
+    },
+    environment: {
+      COMPOSER_ALLOW_SUPERUSER: 1,
+      COMPOSER_MEMORY_LIMIT: '-1',
+      PHP_MEMORY_LIMIT: '1G',
+    },
+    remoteFiles: {
+      _php: '/usr/local/etc/php/conf.d/xxx-lando-default.ini',
+      vhosts: '/etc/apache2/sites-enabled/000-default.conf',
+      php: '/usr/local/etc/php/conf.d/zzz-lando-my-custom.ini',
+    },
+    sources: [],
+    suffix: '4',
+    ssl: false,
+    via: 'apache',
+    volumes: ['/usr/local/bin'],
+    webroot: '.',
+    nginxServiceType: 'php-nginx',
+  },
+  parent: '_appserver',
+  builder: (parent, config) => class LandoPhp extends parent {
+    constructor(id, options = {}, factory) {
+      options = parseConfig(_.merge({}, config, options));
+      // Mount our default php config
+      options.volumes.push(`${options.confDest}/${options.defaultFiles._php}:${options.remoteFiles._php}`);
+
+      // Shift on the docker entrypoint if this is a more recent version
+      if (options.version !== 'custom' && semver.gt(semver.coerce(options.version), '5.5.0')) {
+        options.command.unshift('docker-php-entrypoint');
+      }
+
+      // If xdebug is set to "true" then map it to "debug"
+      if (options.xdebug === true) options.xdebug = 'debug';
+
+      // If this is a legacy php version then switch the suffix
+      if (_.includes(options.gen3, options.version)) options.suffix = '3';
+      if (_.includes(options.gen2, options.version)) options.suffix = '2';
+
+      // Build the php
+      const php = {
+        image: _.get(options, 'image') ?
+          options.image : `devwithlando/php:${options.version}-${options.phpServer}-${options.suffix}`,
+        environment: _.merge({}, options.environment, {
+          PATH: options.path.join(':'),
+          LANDO_WEBROOT: `/app/${options.webroot}`,
+          XDEBUG_CONFIG: xdebugConfig(options._app.env.LANDO_HOST_IP),
+          XDEBUG_MODE: (options.xdebug === false) ? 'off' : options.xdebug,
+        }),
+        networks: (_.startsWith(options.via, 'nginx')) ? {default: {aliases: ['fpm']}} : {default: {}},
+        ports: (_.startsWith(options.via, 'apache') && options.version !== 'custom') ? ['80'] : [],
+        volumes: options.volumes,
+        command: options.command.join(' '),
+      };
+      options.info = {via: options.via};
+
+      // Add our composer things to run step
+      if (!_.isEmpty(options.composer)) {
+        const commands =
+          require('../utils/get-install-commands')(options.composer, pkger, ['composer', 'global', 'require', '-n']);
+        addBuildStep(commands, options._app, options.name, 'build_internal');
+      }
+
+      // Add activate steps for xdebug
+      if (options.xdebug) {
+        addBuildStep(['docker-php-ext-enable xdebug'], options._app, options.name, 'build_as_root_internal');
+      }
+
+      // Install the desired composer version
+      if (options.composer_version) {
+        const commands = [`/helpers/install-composer.sh ${options.composer_version}`];
+        addBuildStep(commands, options._app, options.name, 'build_internal', true);
+      }
+
+      // Add in nginx if we need to
+      if (_.startsWith(options.via, 'nginx')) {
+        // Set another lando service we can pass down the stream
+        const nginxOpts = nginxConfig(options);
+
+        // Merge in any user specifified
+        const PhpNginx = factory.get(nginxOpts.type);
+        const data = new PhpNginx(nginxOpts.name, nginxOpts);
+        // If the user has overriden this service lets make sure we include that as well
+        const userOverrides = _.get(options, `_app.config.services.${nginxOpts.name}.overrides`, {});
+        data.data.push({
+          services: _.set({}, nginxOpts.name, userOverrides),
+          version: _.get(data, 'data[0].version'),
+        });
+        // Add a depends_on to make sure nginx waits for php-fpm to be up.
+        data.data.push({
+          services: _.set({}, nginxOpts.name, {'depends_on': [options.name]}),
+          version: _.get(data, 'data[0].version'),
+        });
+        // This is a trick to basically replicate what happens upstream
+        options._app.add(data);
+        options._app.info.push(data.info);
+        // Indicate the relationship on the primary service
+        options.info.served_by = nginxOpts.name;
+      }
+
+      // Add in the php service and push downstream
+      options.sources.push({services: _.set({}, options.name, php)});
+      super(id, options, ..._.flatten(options.sources));
+    };
+  },
+};

package/node_modules/@lando/php/config/default-ssl.conf

@@ -0,0 +1,188 @@
+<VirtualHost *:80>
+  # WHAT IN THE WORLD HAPPENED TO YOU
+  # The ServerName directive sets the request scheme, hostname and port that
+  # the server uses to identify itself. This is used when creating
+  # redirection URLs. In the context of virtual hosts, the ServerName
+  # specifies what hostname must appear in the request's Host: header to
+  # match this virtual host. For the default virtual host (this file) this
+  # value is not decisive as it is used as a last resort host regardless.
+  # However, you must set it for any further virtual host explicitly.
+  ServerName appserver
+
+  ServerAdmin webmaster@localhost
+  DocumentRoot ${LANDO_WEBROOT}
+  <Directory />
+    Options Indexes FollowSymLinks
+    AllowOverride All
+    Order allow,deny
+    Allow from all
+    Require all granted
+  </Directory>
+
+  # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
+  # error, crit, alert, emerg.
+  # It is also possible to configure the loglevel for particular
+  # modules, e.g.
+  #LogLevel info ssl:warn
+
+  ErrorLog ${APACHE_LOG_DIR}/error.log
+  CustomLog ${APACHE_LOG_DIR}/access.log combined
+
+  # For most configuration files from conf-available/, which are
+  # enabled or disabled at a global level, it is possible to
+  # include a line for only one particular virtual host. For example the
+  # following line enables the CGI configuration for this host only
+  # after it has been globally disabled with "a2disconf".
+  #Include conf-available/serve-cgi-bin.conf
+
+  # Pass some common ENVs, its ok if this fails
+  SetEnv BACKDROP_SETTINGS ${BACKDROP_SETTINGS}
+  SetEnvIf x-forwarded-proto https HTTPS=on
+
+</VirtualHost>
+
+<IfModule mod_ssl.c>
+  <VirtualHost *:443>
+    ServerAdmin webmaster@localhost
+    ServerName appserver
+
+    DocumentRoot ${LANDO_WEBROOT}
+    <Directory />
+      Options Indexes FollowSymLinks
+      AllowOverride All
+      Order allow,deny
+      Allow from all
+      Require all granted
+    </Directory>
+    # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
+    # error, crit, alert, emerg.
+    # It is also possible to configure the loglevel for particular
+    # modules, e.g.
+    #LogLevel info ssl:warn
+
+    ErrorLog ${APACHE_LOG_DIR}/error.log
+    CustomLog ${APACHE_LOG_DIR}/access.log combined
+
+    # For most configuration files from conf-available/, which are
+    # enabled or disabled at a global level, it is possible to
+    # include a line for only one particular virtual host. For example the
+    # following line enables the CGI configuration for this host only
+    # after it has been globally disabled with "a2disconf".
+    #Include conf-available/serve-cgi-bin.conf
+
+    #   SSL Engine Switch:
+    #   Enable/Disable SSL for this virtual host.
+    SSLEngine on
+
+    #   A self-signed (snakeoil) certificate can be created by installing
+    #   the ssl-cert package. See
+    #   /usr/share/doc/apache2/README.Debian.gz for more info.
+    #   If both key and certificate are stored in the same file, only the
+    #   SSLCertificateFile directive is needed.
+    SSLCertificateFile "/certs/cert.crt"
+    SSLCertificateKeyFile "/certs/cert.key"
+
+    #   Server Certificate Chain:
+    #   Point SSLCertificateChainFile at a file containing the
+    #   concatenation of PEM encoded CA certificates which form the
+    #   certificate chain for the server certificate. Alternatively
+    #   the referenced file can be the same as SSLCertificateFile
+    #   when the CA certificates are directly appended to the server
+    #   certificate for convenience.
+    #SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt
+
+    #   Certificate Authority (CA):
+    #   Set the CA certificate verification path where to find CA
+    #   certificates for client authentication or alternatively one
+    #   huge file containing all of them (file must be PEM encoded)
+    #   Note: Inside SSLCACertificatePath you need hash symlinks
+    #    to point to the certificate files. Use the provided
+    #    Makefile to update the hash symlinks after changes.
+    #SSLCACertificatePath /etc/ssl/certs/
+    #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt
+
+    #   Certificate Revocation Lists (CRL):
+    #   Set the CA revocation path where to find CA CRLs for client
+    #   authentication or alternatively one huge file containing all
+    #   of them (file must be PEM encoded)
+    #   Note: Inside SSLCARevocationPath you need hash symlinks
+    #    to point to the certificate files. Use the provided
+    #    Makefile to update the hash symlinks after changes.
+    #SSLCARevocationPath /etc/apache2/ssl.crl/
+    #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl
+
+    #   Client Authentication (Type):
+    #   Client certificate verification type and depth.  Types are
+    #   none, optional, require and optional_no_ca.  Depth is a
+    #   number which specifies how deeply to verify the certificate
+    #   issuer chain before deciding the certificate is not valid.
+    #SSLVerifyClient require
+    #SSLVerifyDepth  10
+
+    #   SSL Engine Options:
+    #   Set various options for the SSL engine.
+    #   o FakeBasicAuth:
+    #  Translate the client X.509 into a Basic Authorisation.  This means that
+    #  the standard Auth/DBMAuth methods can be used for access control.  The
+    #  user name is the `one line' version of the client's X.509 certificate.
+    #  Note that no password is obtained from the user. Every entry in the user
+    #  file needs this password: `xxj31ZMTZzkVA'.
+    #   o ExportCertData:
+    #  This exports two additional environment variables: SSL_CLIENT_CERT and
+    #  SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
+    #  server (always existing) and the client (only existing when client
+    #  authentication is used). This can be used to import the certificates
+    #  into CGI scripts.
+    #   o StdEnvVars:
+    #  This exports the standard SSL/TLS related `SSL_*' environment variables.
+    #  Per default this exportation is switched off for performance reasons,
+    #  because the extraction step is an expensive operation and is usually
+    #  useless for serving static content. So one usually enables the
+    #  exportation for CGI and SSI requests only.
+    #   o OptRenegotiate:
+    #  This enables optimized SSL connection renegotiation handling when SSL
+    #  directives are used in per-directory context.
+    #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
+    <FilesMatch "\.(cgi|shtml|phtml|php)$">
+        SSLOptions +StdEnvVars
+    </FilesMatch>
+    <Directory /usr/lib/cgi-bin>
+        SSLOptions +StdEnvVars
+    </Directory>
+
+    #   SSL Protocol Adjustments:
+    #   The safe and default but still SSL/TLS standard compliant shutdown
+    #   approach is that mod_ssl sends the close notify alert but doesn't wait for
+    #   the close notify alert from client. When you need a different shutdown
+    #   approach you can use one of the following variables:
+    #   o ssl-unclean-shutdown:
+    #  This forces an unclean shutdown when the connection is closed, i.e. no
+    #  SSL close notify alert is send or allowed to received.  This violates
+    #  the SSL/TLS standard but is needed for some brain-dead browsers. Use
+    #  this when you receive I/O errors because of the standard approach where
+    #  mod_ssl sends the close notify alert.
+    #   o ssl-accurate-shutdown:
+    #  This forces an accurate shutdown when the connection is closed, i.e. a
+    #  SSL close notify alert is send and mod_ssl waits for the close notify
+    #  alert of the client. This is 100% SSL/TLS standard compliant, but in
+    #  practice often causes hanging connections with brain-dead browsers. Use
+    #  this only for browsers where you know that their SSL implementation
+    #  works correctly.
+    #   Notice: Most problems of broken clients are also related to the HTTP
+    #   keep-alive facility, so you usually additionally want to disable
+    #   keep-alive for those clients, too. Use variable "nokeepalive" for this.
+    #   Similarly, one has to force some clients to use HTTP/1.0 to workaround
+    #   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
+    #   "force-response-1.0" for this.
+    BrowserMatch "MSIE [2-6]" \
+        nokeepalive ssl-unclean-shutdown \
+        downgrade-1.0 force-response-1.0
+    # MSIE 7 and newer should be able to use keepalive
+    BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown
+
+    # Pass some common ENVs, its ok if this fails
+    SetEnv BACKDROP_SETTINGS ${BACKDROP_SETTINGS}
+    SetEnvIf x-forwarded-proto https HTTPS=on
+
+  </VirtualHost>
+</IfModule>

package/node_modules/@lando/php/config/default-ssl.conf.tpl

@@ -0,0 +1,30 @@
+server {
+    listen       443 ssl;
+    listen       80;
+    listen   [::]:80 default ipv6only=on;
+    server_name  localhost;
+
+    ssl_certificate      /certs/cert.crt;
+    ssl_certificate_key  /certs/cert.key;
+
+    ssl_session_cache    shared:SSL:1m;
+    ssl_session_timeout  5m;
+
+    ssl_ciphers  HIGH:!aNULL:!MD5;
+    ssl_prefer_server_ciphers  on;
+
+    root "{{LANDO_WEBROOT}}";
+    index index.php index.html index.htm;
+
+    location ~ \.php$ {
+        fastcgi_split_path_info ^(.+?\.php)(/.*)$;
+        fastcgi_pass fpm:9000;
+        fastcgi_index  index.php;
+        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
+        fastcgi_buffers 256 128k;
+        fastcgi_connect_timeout 300s;
+        fastcgi_send_timeout 300s;
+        fastcgi_read_timeout 300s;
+        include fastcgi_params;
+    }
+}