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

Review of second deploy #342

Merged
merged 2 commits into from
Jan 29, 2025
Merged

Review of second deploy #342

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ed1d093
Review of second deploy
seddonym Dec 20, 2024
b9e0e9b
Merge branch 'main' into seddonym-second-deploy
hjwp Jan 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion chapter_18_second_deploy.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,14 +38,20 @@ Let's make a little checklist of pre-deployment tasks:
3. We deploy to staging, and run our FTs against staging.
4. Now we can deploy to prod.

// DAVID: By the time I got to this chapter, I had cancelled my digital ocean subscription
// from the earlier chapter as it was coming out of the free period and I hadn't realised I would need it again.
// Perhaps you should consider mentioning at end of the earlier deployment chapter that they'll need to keep the
// subscription active if they want to follow along with this chapter. Even better, maybe find a way of making
// these chapters closer together?


TIP: A deployment checklist like this should be a temporary measure.
Once you've worked through it manually a few times,
you should be looking to take the next step in automation,
continuous deployment straight using a CI/CD pipeline.
We'll touch on this in <<chapter_25_CI>>.



=== A Full Test Run Locally

Of course, under the watchful eye of the Testing Goat,
Expand Down Expand Up @@ -235,6 +241,11 @@ At this point you have two choices:

2. Learn about data migrations. See <<data-migrations-appendix>>.

// DAVID: The option is not such much to 'learn about data migrations' as to 'perform a data migration'.
// A third option is to manually edit the data on the site. If all we have is a staging site it's
// a reasonable thing to do. I wonder if rather than getting into any of this, though, you could just
// be prescriptive and get them to delete the db.


==== How to Delete the Database on the Staging Server

Expand Down
Loading