Officially Shutdown old Drupal Docs Site ETA: JUNE 25th

[jpvajda]

In June our contract with our vendor who hosted our old Docs Site ends, we want to the following:

0. Decide on approach to temporarily host the site.
1. shutdown the old site completely
2. copy all site content to a database file type
3. store that some place so it's accessible if needed by the Docs Team

as a note: we don't need to have this be a readable file, it can be accessed by importing into the database type.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be automatically closed if no further activity occurs. Thank you for your contributions.

[austin-schaefer]

Nice try stale bot! We still need to do this.

[jpvajda]

@austin-schaefer 😆 -stalebot's entire existence is to remind you of things.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be automatically closed if no further activity occurs. Thank you for your contributions.

[jpvajda]

@austin-schaefer do you have any updates on the timing of the shut down of the old drupal site? I'd like to determine what sprint this work should go into. A target date of when this should occur would be helpful. 👍

[austin-schaefer]

Hey @jpvajda , AFAIK it's still the June timeframe you mentioned in the initial issue description.

[jpvajda]

@austin-schaefer could you narrow it down to a week when this has to occur?

[austin-schaefer]

@jpvajda : Looks like it's June 25, but might be good to confirm with @roadlittledawn who was more involved with the details of that.

[zstix]

We should focus on this work no later than [DevEn] Sprint 6, to ensure that we are well ahead of this deadline.

[jpvajda]

This was done after migration, so I'll check with austin if this is enough.

[rhetoric101]

@jpvajda and @austin-schaefer, I'm not sure what the costs are to continue, but I've had a few instances where I've had to consult the old Drupal site to solve some current doc issues (perhaps from the migration).

[roadlittledawn]

i just backed up the dev and prod databases and uploaded to Developer Enablement team Google Drive > Drupal Backups. and a mirror of our repo still exists in enterprise github.

[austin-schaefer]

@roadlittledawn . Nice, do we have documentation on how to access/browse those database backups?

[roadlittledawn]

@austin-schaefer negatory re: documentation. not really sure how we'd provide that to y'all. without the site actually running, not sure how useable that is for y'all. you could browse the data in something like phpmyadmin. but that's just arcane database tables. you could also take the database file and spin up LAMP on your machine or via Docker, but that's an arduous process as well.

@rhetoric101 what kinds of things do you typically consult the old site for? to get HTML for a given node? image files? taxonomy?

[rhetoric101]

@roadlittledawn, not often, but sometimes it's nice to have Drupal as a resource to get perspective on what we used to do when I'm troubleshooting something on the current site--even to think through taxonomy issues. The stuff I'm typically looking for in Drupal is fixes for broken links or missing images. I'm probably an outlier, though.

[austin-schaefer]

@roadlittledawn @jpvajda : I think when we first scoped this out we talked about a VM image as one idea, so we could just spin it up locally or in a cloud environment somewhere to take a look.

@rhetoric101 FWIW I don't think you're an outlier, I know multiple other writers have used the site in the last 30 days alone. Moderation history is particularly important for compliance and change history.

[jpvajda]

@austin-schaefer the basic idea was to just provide just the database of content for reference, but if you are talking about hosting a back up site, why not just pay Acquia some nominal amount to do that for as long as you need it up and running? I don't know the cost, but to run an "offline" site that is only accessible through a login, may not be that costly and it avoids complexity of working with a VM and keep a live site up.

If you need to snapshot a VM of a Drupal site their may be solutions for that a well, so perhaps confirm if running it on Acquia isn't doable, then we can look at a VM solution. something like this perhaps? https://docs.drupalvm.com/en/latest/other/docker/

[jpvajda]

blocked until we make a call on how to proceed, waiting on input from @austin-schaefer

[jpvajda]

@Broseberg is going to discuss with @austin-schaefer how to proceed here as the VM idea may be a bit complex to try to support for DevEn and also run locally for the Docs Team, @roadlittledawn did say he was going test out running a VM of the Drupal site locally as he wanted to experiment a bit 🧪

[roadlittledawn]

i was able to get the drupal site dockerized and working. it's still rudimentary, but seems to work. repo is in github enterprise > nr1-dev-experience/docs-drupal-backup-docker if anyone wants to play with it. the reqs are:

• you need the backup .sql file
• you need KB Kanrisha password to log into admin part of the site

[jpvajda]

@austin-schaefer @Broseberg -- @roadlittledawn found a way to spin the old site up on Docker, the repo can be found above? 😄 Does this work for your needs? I checked it out and it LGTM.

[austin-schaefer]

Oh wow that's amazing! @roadlittledawn I'll look into getting a writer to test this out and socialize it with the docs team

[roadlittledawn]

@austin-schaefer per that README it'll likely take a bit of finagling and anyone running will need the SQL file and KB Kanrisha creds. i'm happy to walk through / provide with any TW

[Broseberg]

Nice! @rhetoric101 would you be interested in testing what Clang put together?

[jpvajda]

closing as the engineering work is done for this now it's a matter of just getting someone familiar with the process to spin up the docker instance of the site.