In Craft CMS 3.1 the long awaited project config feature was added, which, when an administrative setting (channel is added, field is created or updated, assigned to a section, or plugin installed) is updated, the project.yaml file in the config folder will store the change, you can then "sync" those changes to the production database when deploying your changes, here is how our team utilize this feature.
If you're using Laravel Forge as your hosting and provisioning tool, you might come across instances where you need to connect to a remote database via a kocal GUI tool like Sequel Pro or HeidiSQL, but Forge by default only allows SSH connections, here is how to get around it.
Depending on your own and your team's workflow, disabling the ability for clients and developers to update the CMS and plugins in a production environment might be a smart thing to do to simplifiy your deployment strategy, here is how.
If you click the little gear icon in the entry listing page in your control panel, you can pick which fields to display value of for each item in the list, by default the title and date is shown, but if you have images or another short field that would be nice to see in the list, you can add it.
Ngrok is a tool that I and other developers use to create temporary links that route traffic into your local webserver, however out-of-the-box there are some issues when using ngrok with CraftCMS due to how url and asset paths are generated.