{"id":8846,"date":"2016-11-04T16:17:22","date_gmt":"2016-11-04T16:17:22","guid":{"rendered":"https:\/\/www.process.st\/templates\/software-deployment-3\/"},"modified":"2024-02-28T20:50:50","modified_gmt":"2024-02-28T20:50:50","slug":"software-deployment-3","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/software-deployment-3\/","title":{"rendered":"Software Deployment"},"content":{"rendered":"<section id=\"cimpull-pi-ver-200\">\n<h2> CIMPull &quot;Pi&quot; ver. 2.0.0 <\/h2>\n<div class=\"image-content\">\n<figure>\n   <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/n9JN0gLcIF7V5iMuR9VHfg.png\" alt=\"CIMPull 2.0.0 Beta Release: 1\/02\/16\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/n9JN0gLcIF7V5iMuR9VHfg.png\" \/> <\/a><figcaption>\n     CIMPull 2.0.0 Beta Release: 1\/02\/16<br \/>\n   <\/figcaption><\/figure>\n<\/p><\/div>\n<div class=\"text-content\">\n<pre>CIMPull version 2.0.0: Release Notes<strong><u><br \/><br \/><\/u><\/strong><\/pre>\n<p><strong><u>Key Features<\/u><\/strong><\/p>\n<p><em><\/em><strong>i. Registration Portal :&nbsp;<\/strong><\/p>\n<ol>\n<li>Login and Registration<\/li>\n<li><strong><\/strong>User Management&nbsp;<\/li>\n<li>Inventory<\/li>\n<li>BoM Creation<\/li>\n<\/ol>\n<p><strong>ii. Administration Panel<\/strong><\/p>\n<ol>\n<li>User Management<\/li>\n<li>Organization Management<\/li>\n<li>User and Roles<\/li>\n<li>Master Inventory<\/li>\n<li>Shipping and Purchase Orders<\/li>\n<\/ol>\n<\/p><\/div>\n<\/section>\n<section id=\"preparation\">\n<h2> Preparation: <\/h2>\n<\/section>\n<section id=\"gather-the-code-youre-deploying\">\n<h2> Gather the code you're deploying <\/h2>\n<div class=\"text-content\">\n<p>First things first, your software deployment needs to kick off with <strong>collecting the code that needs implementing<\/strong>. Although an obvious step, it is vital that you are certain that the update you later apply is the correct one.<\/p>\n<p>This can be done by checking the completed user stories within your project management software or by checking the original message which prompted you to start off the deployment process. Either way, head to the<strong> correct fork in your code repository<\/strong> and get a hold of the update you need to implement.<\/p>\n<p><strong>Record a copy<\/strong> of the code using the <strong>form field<\/strong> below.<\/p>\n<\/p><\/div>\n<div class=\"file-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Code To Be Deployed <\/label> <\/p>\n<div class=\"file-container\">\n    <button type=\"button\" disabled=\"disabled\" class=\"btn btn-default\"> <i class=\"fa fa-upload btn-icon\"><\/i> File will be uploaded here <\/button>\n   <\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n<section id=\"enter-version-release-notes\">\n<h2> Enter version release notes <\/h2>\n<div class=\"text-content\">\n<p>This is a nice and easy step to follow up with - you should now <strong>enter your code version's release notes in the form fields below<\/strong>.<\/p>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Version Number <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<div class=\"textarea-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Release Notes <\/label><br \/>\n   <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled=\"disabled\" class=\"form-control\"><\/textarea>\n  <\/div>\n<\/p><\/div>\n<div class=\"textarea-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Deployment Script Variables <\/label><br \/>\n   <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled=\"disabled\" class=\"form-control\"><\/textarea>\n  <\/div>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>Although mostly for documentation purposes, this can <strong>greatly help<\/strong> in the event that you need to <strong>roll back to a particular update<\/strong>, or wish to track down the moment when a bug first occurs.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"check-that-the-required-server-is-running-smoothly\">\n<h2> Check that the required server is running smoothly <\/h2>\n<div class=\"image-content\">\n<figure>\n   <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/nmWfwug3UquQ43tTLpVGJg.png\" alt=\"Check that the required server is running smoothly\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/nmWfwug3UquQ43tTLpVGJg.png\" \/> <\/a><br \/>\n  <\/figure>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>This will vary depending on your team's setup and the project you're working on, but in general, you must now<strong> check that the server<\/strong> you need to upload your code to<strong> is set up correctly and running smoothly<\/strong>.<\/p>\n<p>If you only use one server, this should be easy. If, however, you need to organize a new server for your&nbsp;code, we have a handy little <strong><a href=\"https:\/\/www.process.st\/templates\/ubuntu-server-setup-process\/\" rel=\"nofollow noopener\" target=\"_blank\">server setup process<\/a><\/strong> to help you on your way.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"configure-your-staging-environment\">\n<h2> Configure your staging environment <\/h2>\n<div class=\"text-content\">\n<p>In order for your pre-production tests to be accurate, you need to ensure that your <strong>staging environment<\/strong> is set up correctly. To this end (and only if required), you need to make any necessary <strong>configuration changes<\/strong> to the environment, ready for your update to be put through its paces.<\/p>\n<p>The method for this will vary depending on the setup of your server and staging environment, along with the configs that are required. In general, though, you'll want to <strong>create a backup<\/strong> <strong>of your production server<\/strong>, <strong>copy<\/strong> that backup, <strong>make your alterations<\/strong>, then <strong>update your test server<\/strong> with the altered backup.<\/p>\n<p>Don't forget to <strong>restart the server<\/strong> after any changes are made!<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"testing\">\n<h2> Testing: <\/h2>\n<\/section>\n<section id=\"deploy-the-update-to-your-test-environment\">\n<h2> Deploy the update to your test environment <\/h2>\n<div class=\"text-content\">\n<p>The time has come in your software deployment for you to test the updates in the staging environment. To start us off, <strong>upload your new code to the testing environment<\/strong>.<\/p>\n<p>This can be done (if using open source development) by <strong>merging<\/strong> the appropriate <strong>repo branch<\/strong> with your test environment and selecting the upgrade to be &quot;Immediately&quot;.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"test-the-code\">\n<h2> Test the code <\/h2>\n<div class=\"image-content\">\n<figure>\n   <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/vx4EoG81Ia2fOaxYzg9CnQ.png\" alt=\"Test the code\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/vx4EoG81Ia2fOaxYzg9CnQ.png\" \/> <\/a><br \/>\n  <\/figure>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>Whether you're using automatic tests, manual tests or (better yet) a mixture of the two, now is the time to run them.<strong> Put the new update through its paces<\/strong> in the test environment and<strong> note your findings<\/strong>.<\/p>\n<p>At the very least you'll want to be running <strong>several integration&nbsp;and unit tests<\/strong>, but a good practice is to also just go through the test environment and see if any new vulnerabilities have been exposed by the update through simulating a normal user.<\/p>\n<p>For example, if the update is to your login page, make sure that no hidden fields or data is shown by entering an incorrect password, etc. Be <strong>as thorough as possible<\/strong> and note down your findings for review shortly.<\/p>\n<p>If you haven't got set tests already set up, why not take a look at our <strong><a href=\"https:\/\/www.process.st\/templates\/software-testing-tut\" rel=\"nofollow noopener\" target=\"_blank\">software testing tutorial<\/a><\/strong>&nbsp;to get you off the ground?<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"review-the-results\">\n<h2> Review the results <\/h2>\n<div class=\"text-content\">\n<p>This stage in your software deployment is pretty self-explanatory. You must now go over the results of your tests and <strong>assess whether or not the code is fit to deploy<\/strong>. <strong>Record the status of the test results in the form field<\/strong> below (which can be edited if you desire).<\/p>\n<\/p><\/div>\n<div class=\"select-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Test Results <\/label><br \/>\n   <select disabled=\"disabled\" class=\"form-control\"><option value=\"An option will be selected here\">An option will be selected here<\/option><\/select>\n  <\/div>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>Now, we do not mean that the&nbsp;<em>slightest<\/em> error or bug should cause the delay of a major update; <strong>there will always be small errors<\/strong> which are missed or caused by an unforeseen effect. However, <strong>any problems<\/strong> caused by the code should be <strong>weighed up against the benefit (and functionality) of the update<\/strong>.<\/p>\n<p>For example, it does not make sense to delay an entire feature's release because of a relatively harmless bug, such as a user's date of birth no longer showing on their profile.<\/p>\n<p>Assess the test results, <strong>notifying the developers and returning the code (with a copy of the test results) if it is not up to scratch<\/strong>. Otherwise, note any new minor problems as a new user stories in your project management software and carry on this checklist.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"deployment\">\n<h2> Deployment: <\/h2>\n<\/section>\n<section id=\"copy-your-update-to-the-production-environment\">\n<h2> Copy your update to the production environment <\/h2>\n<div class=\"text-content\">\n<p>Now that you're certain the update won't completely kill your site, it's time to<strong> merge it into the production environment<\/strong>. This is done in exactly the same manner as with your test environment, and so should pose little to no problems at this stage.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"run-any-necessary-devops-scripts\">\n<h2> Run any necessary DevOps scripts <\/h2>\n<div class=\"image-content\">\n<figure>\n   <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/lzdIVy6RWBFeJciyD-hFKw.png\" alt=\"Run any necessary DevOps scripts\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/lzdIVy6RWBFeJciyD-hFKw.png\" \/> <\/a><br \/>\n  <\/figure>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>In the final step before you set the update to be live, you need to assess whether it is necessary to <strong>run any DevOps scripts in order to update your databases<\/strong>. If so, these scripts must be executed now in order to support the code.<\/p>\n<p>Use the<strong> sub-checklist<\/strong> below to keep track of the areas you still need to run scripts in.<\/p>\n<\/p><\/div>\n<div class=\"multi-select-content form-field-content\">\n<ul class=\"items\">\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       1\n     <\/div>\n<\/p><\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/p><\/div>\n<div class=\"item-name-static\">\n      Front End\n    <\/div>\n<\/li>\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       2\n     <\/div>\n<\/p><\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/p><\/div>\n<div class=\"item-name-static\">\n      Back End\n    <\/div>\n<\/li>\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       3\n     <\/div>\n<\/p><\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/p><\/div>\n<div class=\"item-name-static\">\n      Product\n    <\/div>\n<\/li>\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       4\n     <\/div>\n<\/p><\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/p><\/div>\n<div class=\"item-name-static\">\n      Support\n    <\/div>\n<\/li>\n<\/ul><\/div>\n<div class=\"text-content\">\n<p>Usually, this will only be required when there is a significant updated being deployed, however, you must be incredibly thorough when running these. You need to<strong> ensure that every one of your databases is updated with the correct scripts<\/strong>.<\/p>\n<p>Although the databases you need to update will vary,&nbsp;the <strong>sub-checklist can easily be edited<\/strong> to suit your needs.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"set-your-changes-live\">\n<h2> Set your changes live <\/h2>\n<div class=\"text-content\">\n<p>The big moment is here, and it's to set your changes to be live! <strong>Push your updates<\/strong> in the production environment onto the <strong>live version of the site<\/strong> and rejoice in the gloriously sparkly new updates. <strong>Record the date<\/strong> of the live deployment in the <strong>form field<\/strong> below.<\/p>\n<\/p><\/div>\n<div class=\"date-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Live Date <\/label> <\/p>\n<div class=\"date-container\">\n    <button type=\"button\" disabled=\"disabled\" class=\"btn btn-default\"> <i class=\"fa fa-calendar btn-icon\"><\/i> Date will be set here <\/button>\n   <\/div>\n<\/p><\/div>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>Consider that, if this is a large update, you may want to <strong>schedule and announce some downtime<\/strong> whilst this occurs.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"test-on-the-live-server\">\n<h2> Test on the live server <\/h2>\n<div class=\"text-content\">\n<p>The final step in the software deployment checklist is to <strong>check your live server for bugs<\/strong> once the changes have been applied. This should be as <strong>thorough<\/strong> as possible, as it is much better for your team to notice a bug and record it than leaving the job to your customers.<\/p>\n<p>If you find a <strong>critical bug<\/strong> which cannot be ignored, it may even be worth <strong>considering a server roll-back<\/strong>, but (thanks to your previous checks) this should not occur. Instead, any<strong> minor bugs<\/strong> which are picked up should be <strong>reported as new user stories<\/strong> within your porject management software.<\/p>\n<p>Congratulations on completing the software deployment checklist! Enjoy your new-and-improved product, and don't forget to keep an eye out for new bugs that are spotted down the line.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"sources\">\n<h2> Sources: <\/h2>\n<div class=\"text-content\">\n<p>Josh Berkus on <a href=\"https:\/\/lwn.net\/\" target=\"_blank\" rel=\"nofollow noopener\">LWN.net<\/a> -&nbsp;<a href=\"https:\/\/lwn.net\/Articles\/562333\/\" target=\"_blank\" rel=\"nofollow noopener\">The Seven Deadly Sins of Software Deployment<\/a><\/p>\n<p><a href=\"https:\/\/confluence.atlassian.com\/alldoc\/atlassian-documentation-32243719.html\" rel=\"nofollow noopener\" target=\"_blank\">Atlassian Documentation<\/a> -&nbsp;<a href=\"https:\/\/confluence.atlassian.com\/jira\/establishing-staging-server-environments-for-jira-285839559.html\" rel=\"nofollow noopener\" target=\"_blank\">Establishing Staging Server Environments for JIRA<\/a><\/p>\n<p><a href=\"https:\/\/developer.github.com\/\" rel=\"nofollow noopener\" target=\"_blank\">GitHub Developer<\/a> -&nbsp;<a href=\"https:\/\/developer.github.com\/guides\/delivering-deployments\/\" rel=\"nofollow noopener\" target=\"_blank\">Delivering Deployments<\/a><\/p>\n<p><a href=\"https:\/\/gist.github.com\/\" rel=\"nofollow noopener\" target=\"_blank\">GitHub Gist<\/a> -&nbsp;<a href=\"https:\/\/gist.github.com\/oodavid\/1809044\" rel=\"nofollow noopener\" target=\"_blank\">Deploy Your Site With Git<\/a><\/p>\n<p><a href=\"http:\/\/torquemag.io\/author\/byanofsky12\/\" rel=\"nofollow noopener\" target=\"_blank\">Brandon Yanofsky<\/a> -&nbsp;<a href=\"http:\/\/torquemag.io\/2015\/01\/need-start-using-staging-environment\/\" rel=\"nofollow noopener\" target=\"_blank\">Why You Need To Start Using a Staging Environment<\/a><\/p>\n<p><a href=\"http:\/\/www.mobify.com\/blog\/author\/kyle-young\/\" rel=\"nofollow noopener\" target=\"_blank\">Kyle Young<\/a> -&nbsp;<a href=\"http:\/\/www.mobify.com\/blog\/devops-101-best-practices\/\" rel=\"nofollow noopener\" target=\"_blank\">DevOps 101: Best Practices for Optimizing and Automating Your Infrastructure<\/a><\/p>\n<p><a href=\"https:\/\/docs.acquia.com\/\" rel=\"nofollow noopener\" target=\"_blank\">Acquia Help Center<\/a> -&nbsp;<a href=\"https:\/\/docs.acquia.com\/site-factory\/tiers\/paas\/deploy\" rel=\"nofollow noopener\" target=\"_blank\">Deploying Your Code To Production<\/a><\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"relevant-checklists\">\n<h2> Relevant Checklists: <\/h2>\n<div class=\"text-content\">\n<p><a href=\"https:\/\/www.process.st\/templates\/git-workflow\/\" target=\"_blank\" rel=\"nofollow noopener\">Git Workflow<\/a><\/p>\n<p><a href=\"https:\/\/www.process.st\/templates\/user-story-template\/\" target=\"_blank\" rel=\"nofollow noopener\">User Story Template<\/a><\/p>\n<p><a href=\"https:\/\/www.process.st\/templates\/sprint-planning\/\" target=\"_blank\" rel=\"nofollow noopener\">Sprint Planning<\/a><\/p>\n<p><a href=\"https:\/\/www.process.st\/templates\/scrum-project-management\/\" target=\"_blank\" rel=\"nofollow noopener\">Scrum Project Management<\/a><\/p>\n<p><a href=\"https:\/\/www.process.st\/templates\/software-testing-tutorial\/\" target=\"_blank\" rel=\"nofollow noopener\">Software Testing Tutorial<\/a><\/p>\n<p><a href=\"https:\/\/www.process.st\/templates\/software-debugging-process\/\" target=\"_blank\" rel=\"nofollow noopener\">Software Debugging Process<\/a><\/p>\n<\/p><\/div>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>CIMPull &quot;Pi&quot; ver. 2.0.0 CIMPull 2.0.0 Beta Release: 1\/02\/16 CIMPull version 2.0.0: Release Notes Key Features i. Registration Portal :&nbsp; Login and Registration User Management&nbsp; Inventory BoM Creation ii. Administration Panel User Management Organization Management User and Roles Master Inventory Shipping and Purchase Orders Preparation: Gather the code you're deploying First things first, your software [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":4746,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"ep_exclude_from_search":false,"cover_icon_emoji":"","cover_icon_url":"","tasks_count":"17","template_description":"Run this checklist every time you need to deploy an update to your software","template_id":"p4_uQ4J687k1dAvG1JRGvw","task_0":"CIMPull &quot;Pi&quot; ver. 2.0.0","task_slug_0":"cimpull-pi-ver-200","task_1":"Preparation:","task_slug_1":"preparation","task_2":"Gather the code you're deploying","task_slug_2":"gather-the-code-youre-deploying","task_3":"Enter version release notes","task_slug_3":"enter-version-release-notes","task_4":"Check that the required server is running smoothly","task_slug_4":"check-that-the-required-server-is-running-smoothly","task_5":"Configure your staging environment","task_slug_5":"configure-your-staging-environment","task_6":"Testing:","task_slug_6":"testing","task_7":"Deploy the update to your test environment","task_slug_7":"deploy-the-update-to-your-test-environment","task_8":"Test the code","task_slug_8":"test-the-code","task_9":"Review the results","task_slug_9":"review-the-results","task_10":"Deployment:","task_slug_10":"deployment","task_11":"Copy your update to the production environment","task_slug_11":"copy-your-update-to-the-production-environment","task_12":"Run any necessary DevOps scripts","task_slug_12":"run-any-necessary-devops-scripts","task_13":"Set your changes live","task_slug_13":"set-your-changes-live","task_14":"Test on the live server","task_slug_14":"test-on-the-live-server","task_15":"Sources:","task_slug_15":"sources","task_16":"Relevant Checklists:","task_slug_16":"relevant-checklists","task_17":"","task_slug_17":"","task_18":"","task_slug_18":"","task_19":"","task_slug_19":"","task_20":"","task_slug_20":"","task_21":"","task_slug_21":"","task_22":"","task_slug_22":"","task_23":"","task_slug_23":"","task_24":"","task_slug_24":"","task_25":"","task_slug_25":"","task_26":"","task_slug_26":"","task_27":"","task_slug_27":"","task_28":"","task_slug_28":"","task_29":"","task_slug_29":"","task_30":"","task_slug_30":"","task_31":"","task_slug_31":"","task_32":"","task_slug_32":"","task_33":"","task_slug_33":"","task_34":"","task_slug_34":"","task_35":"","task_slug_35":"","task_36":"","task_slug_36":"","task_37":"","task_slug_37":"","task_38":"","task_slug_38":"","task_39":"","task_slug_39":"","task_40":"","task_slug_40":"","task_41":"","task_slug_41":"","task_42":"","task_slug_42":"","task_43":"","task_slug_43":"","task_44":"","task_slug_44":"","task_45":"","task_slug_45":"","task_46":"","task_slug_46":"","task_47":"","task_slug_47":"","task_48":"","task_slug_48":"","task_49":"","task_slug_49":"","task_50":"","task_slug_50":"","task_51":"","task_slug_51":"","task_52":"","task_slug_52":"","task_53":"","task_slug_53":"","task_54":"","task_slug_54":"","task_55":"","task_slug_55":"","task_56":"","task_slug_56":"","task_57":"","task_slug_57":"","task_58":"","task_slug_58":"","task_59":"","task_slug_59":"","task_60":"","task_slug_60":"","task_61":"","task_slug_61":"","task_62":"","task_slug_62":"","task_63":"","task_slug_63":"","task_64":"","task_slug_64":"","task_65":"","task_slug_65":"","task_66":"","task_slug_66":"","task_67":"","task_slug_67":"","task_68":"","task_slug_68":"","task_69":"","task_slug_69":"","task_70":"","task_slug_70":"","task_71":"","task_slug_71":"","task_72":"","task_slug_72":"","task_73":"","task_slug_73":"","task_74":"","task_slug_74":"","task_75":"","task_slug_75":"","task_76":"","task_slug_76":"","task_77":"","task_slug_77":"","task_78":"","task_slug_78":"","task_79":"","task_slug_79":"","task_80":"","task_slug_80":"","task_81":"","task_slug_81":"","task_82":"","task_slug_82":"","task_83":"","task_slug_83":"","task_84":"","task_slug_84":"","task_85":"","task_slug_85":"","task_86":"","task_slug_86":"","task_87":"","task_slug_87":"","task_88":"","task_slug_88":"","task_89":"","task_slug_89":"","task_90":"","task_slug_90":"","task_91":"","task_slug_91":"","task_92":"","task_slug_92":"","task_93":"","task_slug_93":"","task_94":"","task_slug_94":"","task_95":"","task_slug_95":"","task_96":"","task_slug_96":"","task_97":"","task_slug_97":"","task_98":"","task_slug_98":"","task_99":"","task_slug_99":"","footnotes":""},"categories":[7,1],"tags":[],"class_list":["post-8846","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-miscellaneous","category-uncategorized"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/8846","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/comments?post=8846"}],"version-history":[{"count":0,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/8846\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/media\/4746"}],"wp:attachment":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/media?parent=8846"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/categories?post=8846"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/tags?post=8846"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}