# Getting Production Ready **URL:** \ **Category:** Chapter Comments\ **Created:** [May 9, 2018, 11:10pm UTC](https://discourse.sst.dev/t/getting-production-ready/158 "2018-05-09T23:10:24Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![jayair](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/jayair/32/9_2.png) [@jayair](https://discourse.sst.dev/u/jayair)\ **Post date:** [May 9, 2018, 11:10pm UTC](https://discourse.sst.dev/t/getting-production-ready/158/1 "2018-05-09T23:10:24Z")
Link to chapter - [https://serverless-stack.com/chapters/getting-production-ready.html](https://serverless-stack.com/chapters/getting-production-ready.html) ---
**Author:** ![walshe](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/walshe/32/116_2.png) [@walshe](https://discourse.sst.dev/u/walshe)\ **Post date:** [May 18, 2018, 2:37am UTC](https://discourse.sst.dev/t/getting-production-ready/158/2 "2018-05-18T02:37:19Z")
would it be a good idea for sanity to have an ‘about’ menu somewhere that displays build stage name/version of a) the front end b) each service that the frontend is hitting - at least for non production environments anyway. @jayair ---
**Author:** ![jayair](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/jayair/32/9_2.png) [@jayair](https://discourse.sst.dev/u/jayair)\ **Post date:** [May 18, 2018, 8:32pm UTC](https://discourse.sst.dev/t/getting-production-ready/158/3 "2018-05-18T20:32:34Z")
Hmm I’m not sure if I get what you mean. ---
**Author:** ![walshe](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/walshe/32/116_2.png) [@walshe](https://discourse.sst.dev/u/walshe)\ **Post date:** [May 19, 2018, 2:47am UTC](https://discourse.sst.dev/t/getting-production-ready/158/4 "2018-05-19T02:47:31Z")
what I mean is an ‘About’ menu on the toolbar. When its open for example it shows env info e.g client: dev latest notes-service: dev latest other-service: dev latest graphql-service: dev latest ---
**Author:** ![jayair](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/jayair/32/9_2.png) [@jayair](https://discourse.sst.dev/u/jayair)\ **Post date:** [May 19, 2018, 10:25pm UTC](https://discourse.sst.dev/t/getting-production-ready/158/5 "2018-05-19T22:25:46Z")
Hmm do you mean in the [demo app](https://demo2.serverless-stack.com)? ---
**Author:** ![markgargan](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/markgargan/32/903_2.png) [@markgargan](https://discourse.sst.dev/u/markgargan)\ **Post date:** [June 12, 2020, 6:40am UTC](https://discourse.sst.dev/t/getting-production-ready/158/6 "2020-06-12T06:40:08Z")
Hi guys, this is going to sound a little odd, but I’d no idea that you could configure the AWS environment with code? I was fully prepared to start going through process of creating each environment each table manually. In hindsight, it was naive of me to think that this was the case but maybe mentioning at the the start of the manual configuration stage. It may already be there and I missed it but if it isn’t mentioning that later it will all be configurable by code at a later date might spur the reader on. Thanks, Mark. ---
**Author:** ![jayair](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/jayair/32/9_2.png) [@jayair](https://discourse.sst.dev/u/jayair)\ **Post date:** [June 13, 2020, 10:32pm UTC](https://discourse.sst.dev/t/getting-production-ready/158/7 "2020-06-13T22:32:19Z")
Oh thats a good point! Can I bother you to point out in which of early chapters should we have mentioned this? ---
**Author:** ![markgargan](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/markgargan/32/903_2.png) [@markgargan](https://discourse.sst.dev/u/markgargan)\ **Post date:** [June 14, 2020, 2:46pm UTC](https://discourse.sst.dev/t/getting-production-ready/158/8 "2020-06-14T14:46:35Z")
Honestly, more than likely this is mentioned at the start somewhere. I’m coming back to the tutorial over a period of a few weeks so unfortunately I forget some of the earlier tutorials. Perhaps a link in the top right that would link to the infrastructure as code equivalent for each section as you complete it would keep it fresh in the mind that automation lies at the end? ---
**Author:** ![jayair](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/jayair/32/9_2.png) [@jayair](https://discourse.sst.dev/u/jayair)\ **Post date:** [July 2, 2020, 8:31pm UTC](https://discourse.sst.dev/t/getting-production-ready/158/9 "2020-07-02T20:31:56Z")
Got it. Yeah we are planning to doing a little restructuring soon. So we’ll keep this in mind. ---
**Author:** ![mathewgries](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/mathewgries/32/419_2.png) [@mathewgries](https://discourse.sst.dev/u/mathewgries)\ **Post date:** [December 15, 2020, 3:33am UTC](https://discourse.sst.dev/t/getting-production-ready/158/10 "2020-12-15T03:33:41Z")
In this chapter we are moving files to a newly created “services” directory. One of the files being moved is the package.json file. However, in [https://serverless-stack.com/chapters/deploying-through-seed.html](https://serverless-stack.com/chapters/deploying-through-seed.html), it is stating to run “npm version patch” command from the root. This command fails because there is no longer a package.json file in the root. Should we have a package.json in the root and/or our services folder? ---
**Author:** ![jayair](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/jayair/32/9_2.png) [@jayair](https://discourse.sst.dev/u/jayair)\ **Post date:** [January 3, 2021, 1:18am UTC](https://discourse.sst.dev/t/getting-production-ready/158/12 "2021-01-03T01:18:34Z")
Good catch! This shouldn’t be run at the root. We’ll change the chapter.