Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch Local Development infrastructure to Lando #104

Open
5 of 6 tasks
jlandfried opened this issue Jan 10, 2020 · 0 comments
Open
5 of 6 tasks

Switch Local Development infrastructure to Lando #104

jlandfried opened this issue Jan 10, 2020 · 0 comments

Comments

@jlandfried
Copy link
Contributor

jlandfried commented Jan 10, 2020

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant