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.

Sign up for GitHub

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

Jump to bottom

Access to db from live Labdoo 2.0 site #18

Closed
joefincher opened this issue Jun 29, 2022 · 11 comments
Closed

Access to db from live Labdoo 2.0 site #18

joefincher opened this issue Jun 29, 2022 · 11 comments

Comments

@joefincher
Copy link
Collaborator

Requesting either Linux terminal access or an sql dump of the live Labdoo 2.0 site. The Dev site db has been trimmed to the point that many fields have no data and settings like language have been removed so that only English is available. Testing migration scenarios is highly degraded with the reduced site.

Terminal access is not needed if a simple drush sql-dump command can be run by the site admin and the db made available.
@labdoo-org
Copy link
Contributor

labdoo-org commented Jun 30, 2022 via email

@greggmarshall
Copy link
Collaborator

Jordi, from what I understand, the Labdoo 2.0 doesn't have any of the multi-lingual content. My suggestion is for you to dump the current production site and sanitize any content you feel is sensitive/PII.

@jrosgiralt
Copy link
Collaborator

Thanks Gregg and Joe. My concern is that sanitizing a full dump is hard and fragile. That is, starting from the full dump and trimming it down, with high probability we will be missing certain sensitive private data (like an email or some user-to-user conversation). If the goal is to test multi-lingual content, I wonder whether we can create a sample content example and have dummy translations, and test with that toy example? This might also give you fine grain control of the types of content you want to test.

@greggmarshall
Copy link
Collaborator

Given that approach, Joe I suggest focusing on getting the content type definitions moved to 3.0 (including changing field collections into paragraphs) and we can continue to think about how to get a reasonable data set for the content migration.

@joefincher
Copy link
Collaborator Author

I understand the challenges with sanitizing the live site.

In the Dev there is only story as a field collection. Were others used in the live version?

@jrosgiralt
Copy link
Collaborator

Hi Joe and Gregg, will you attend tomorrow's Labdoo call? we can discuss this during tomorrow's call if so. Thanks.

@joefincher
Copy link
Collaborator Author

joefincher commented Jul 9, 2022 via email

@greggmarshall
Copy link
Collaborator

Did I decline one too many invites? Can you send it to me again?

@labdoo-org
Copy link
Contributor

labdoo-org commented Jul 9, 2022 via email

@greggmarshall
Copy link
Collaborator

yes

@joefincher
Copy link
Collaborator Author

joefincher commented Oct 11, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@greggmarshall @jrosgiralt @labdoo-org @joefincher