9 minute reading time; ~1720 words<\/p>\n\n\n\n
Welcome and hello!<\/p>\n\n\n\n
This post is going to take the work we’ve done so far, and put it where it can be used. We’re going to walk through designing an automated deployment process, and some cleanup that we have to do around the branding as part of taking it to production.<\/p>\n\n\n\n
Let’s dig into it, and put our work in front of the world!<\/p>\n\n\n\n
If you haven’t read the previous posts, I’d suggest you start at An App From Scratch: Part 1 \u2013 What To Build<\/a>. You can also find all the related documents and code here: Building Tailgunner<\/a>.<\/p>\n\n\n\n Let’s take a look at the final card in this feature.<\/p>\n\n\n\n Card<\/strong>: US1-C4<\/p>\n\n\n\n Set up production server and deployment<\/p>\n<\/div>\n\n\n\n Task<\/p>\n<\/div>\n<\/div>\n\n\n\n Create a production web server, and implement a deployment workflow to get our code into production.<\/p>\n\n\n\n Acceptance Criteria<\/strong><\/p>\n\n\n\n Reviewing the system diagram and acceptance criteria, we can break down these tasks:<\/p>\n\n\n\n First of all, I want to lay out the deployment structure on the server.<\/p>\n\n\n\nWhat Do I See?<\/h2>\n\n\n\n
Title<\/h4>\n\n\n\n
Type<\/h4>\n\n\n\n
Description<\/h4>\n\n\n\n
\n
tailgunner.app<\/code>, running the latest main branch code.<\/li>\n\n\n\nWhat I Need To Do<\/h3>\n\n\n\n
\n
Putting It Into Action<\/h2>\n\n\n\n
Set up server environment<\/h4>\n\n\n\n