Skip to content

Switch Local Development infrastructure to Lando #104

@jlandfried

Description

@jlandfried

There was some preliminary work done for this in #67 and #101, but there have been some changes on the Lando end, and we are shifting gears to adopt it as the sole local development infrastructure for the scaffold going forward, and a new issue helps reflect that.

Work for this is being done on the lando branch. There is a TODO.md file that outlines work still to be done, but for tracking purposes here are the pieces that I think are still remaining.

TODO

  • BLACKFIRE: Enable Blackfire in Lando (see this issue and this gist)
    • Update Blackfire docs in docs/tools/blackfire.md
  • WDIO:
    • Disable, remove WDIO configuration
    • Documentation at docs/tools/wdio.md
  • MANNEQUIN:
    • Add mannequin service to Lando config
    • Update Mannequin docs at docs/tools/mannequin.md
  • VARNISH:
    • Determine if we still want a varnish service
    • If yes:
      • add varnish service to .lando.yml
    • If no:
      • Remove docker/default.vcl, docs in docs/tools/varnish.md
  • DOCKER-COMPOSE: Since we're switching from docker-compose to lando it would be confusing to leave the docker-compose functionality in here, documented or not. We should remove config and references to the old docker-compose local infrastructure
    • Remove docker-compose.yml
    • Remove docker directory
  • LOCAL DEVELOPMENT TOOLS:
    • Determine if we need the site-import tooling in appserver
    • If yes:
      • Add terminus commands and scripts for importing a database
      • Add acquia API commands for importing databases

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions