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

Review of second deploy #342

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
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
11 changes: 10 additions & 1 deletion chapter_18_second_deploy.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,11 @@ You can refer back to <<chapter_11_server_prep>> for reminders on Ansible comman


=== Staging Deploy

// 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?

We start with the staging server:

Expand Down Expand Up @@ -152,6 +156,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

Here's how you might do option (1):
Expand Down
Loading