Drift is when your stacks actual configuration is changed and is now different from what CloudFormation expects, This can happen if adhoc or manual changes were made outside of CloudFormation.

CloudFormation will detect if resources have been modified, deleted, in sync or they could be in not checked status(CloudFormation has not checked status of the resource yet).

Cloudformation does not detect drift in nested stacks that belong to that stack.You can however initiate a drift detection to that particular nested stack separately.

The differences will be shown in the drift details on the AWS Console.

For a list of known cases where false positives can occur during drift detection, see the following .

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-stack-drift.html

--

--

So you just got started with Next js and started a new project , or cloned some project or boilerplate from github to check it out.

One issue I came across was that I already had one of my projects running on port 3000 and I couldn’t find a way to change the port!

This is because the port config is embedded into next.

By default they have chosen 3000.

To change the port you have to change your package.json to reflect the new port. The trick is a simple -p <PORT_NUMBER>

"scripts": {
"dev": "next dev -p 8080", // for dev server
"start": "next start -p 8080" // for prod server
},

Hopefully this helps someone!

--

--

Gunschu Blog

Gunschu Blog

31 Followers

Gunschu is creating the world’s greatest coaching platform through groundbreaking tools, advice, knowledge and personal expertise.