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

Add configuration flags for ddev pull - --ignore-db, ignore-files, etc. #405

Closed
beeradb opened this issue Jul 18, 2017 · 10 comments
Closed
Assignees
Milestone

Comments

@beeradb
Copy link
Contributor

beeradb commented Jul 18, 2017

What happened (or feature request):

In #345 we introduced pantheon provider support. This was a big step forward, but there are ways we can improve it.

What you expected to happen:

We should introduce additional flags for ddev pull which allow more control over its behavior. The following flags should be added:

  • --ignore-db (does not download a new database archive and uses most recent version)
  • --ignore-files (does not download a new file archive and uses most recent version)
  • --skip-import (performs the download of files and/or db but does not perform the import)
  • --env=ENV (allows users to target a different environment than the one specified in config)

Related source links or issues:

#345 (comment)

@rickmanelius
Copy link
Contributor

This looks mostly actionable, but probably needs another set of eyes from a UX perspective before we commit to this approach. Also needs prioritization.

@eojthebrave
Copy link

This would be a nice addition. Specifically the option to choose to skip downloading either the files, or the db. I'm using ddev with the Pantheon provider, and being able to update the DB with a fresh copy but not worry about the files directory would be nice. Especially for sites with files directories that are multiple Gigabytes of data.

@rickmanelius
Copy link
Contributor

@eojthebrave We completely agree that this will be a necessary feature in the future. We're in the process of finding additional team members to support this and other requests. I've updated the labels to note that this needs final definition and prioritization. Thanks!

@ultimike
Copy link
Contributor

Agreed - a way to only pull the DB is pretty necessary in the short-term, IMHO. I have sites with multiple-GB-sized files directories that I don't want pulled to my local (that's what Stage File Proxy is for).

@rickmanelius rickmanelius added this to the v1.4.0 milestone Feb 23, 2018
@rickmanelius rickmanelius self-assigned this Mar 23, 2018
@rfay rfay changed the title Add configuration flags for ddev pull Add configuration flags for ddev pull - --ignore-db, ignore-files, etc. May 2, 2018
@dclear dclear modified the milestones: v1.4.0, v1.3.0 May 17, 2018
@dclear dclear removed this from the v1.3.0 milestone May 29, 2018
@dclear dclear added actionable and removed incubate labels Jun 4, 2018
@rickmanelius rickmanelius added this to the v1.2.0 milestone Aug 3, 2018
@rickmanelius
Copy link
Contributor

We need to get this in by next release... it's valuable and I don't believe it's a heavy lift.

@rickmanelius
Copy link
Contributor

We'll want to do this for both Pantheon as well as drud-s3. I think this is one of those low effort, high value items.

@rfay
Copy link
Member

rfay commented Aug 21, 2018

It's just one effort, not separate things.

@eojthebrave
Copy link

Just stopping by to say thanks. This --skip-files feature works great and easily replaces a handful of commands I was using to do this using a combination of terminus and ddev. And saves a lot of time/bandwidth for me. 🙏

@rfay
Copy link
Member

rfay commented Oct 30, 2018

Awesome, thanks! Always love to hear how you're using ddev and what your needs are.

@rfay
Copy link
Member

rfay commented Oct 30, 2018

And looking forward to a drupalize.me training on getting started with ddev and drupal, that would be awesome. We're happy to help with anything it would need. Would love to see what you'd do with that.

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

8 participants