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

chore: bump mysql image version to 8.1 #55

Merged
merged 1 commit into from
Sep 27, 2023
Merged

Conversation

dustin-jw
Copy link
Contributor

Description

This bumps the MySQL version used by sparkpress_db to 8.1, which is compatible with WordPress 6.3.

Closes #27

To Validate

  1. Make sure all PR Checks have passed
  2. Pull down this branch
  3. Stop your running containers (docker compose down)
  4. You may want to delete your images and volumes, but that may not be necessary
  5. Run docker compose build
  6. Run npm start
  7. Visit http://localhost:8000 and confirm that the typical WordPress installation works as expected (or your site works as expected if you didn't delete your DB volume)
  8. Download this DB export and put it in a top-level sql folder
  9. Run npm run import-db
  10. Visit http://localhost:8000 and confirm that there is a post titled "MySQL 8.1 Test" and that the site works normally

Copy link
Contributor

@rise-erpelding rise-erpelding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My local site is working as expected and I had no issues importing or exporting! Nice work!

@dustin-jw dustin-jw force-pushed the chore--update-db-version branch from 71aa7ce to a0a13e3 Compare September 27, 2023 14:33
@dustin-jw dustin-jw merged commit a0a13e3 into main Sep 27, 2023
1 check passed
@dustin-jw dustin-jw deleted the chore--update-db-version branch September 27, 2023 14:34
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

Successfully merging this pull request may close these issues.

Update DB
2 participants