Installation/running a dev localhost and public production

Hello,

How would one go about installing / configuring a dev (localhost) and a production environment?

Ideally, I would like to configure an environment with the following:

1. localhost (dev)
2. testing.example.com (prod dev)
3. example.com (prod)

One would assume, the above is a pretty standard environment.

Can someone point me to some documentation (I've searched, but no luck)?

Installing multiple sites / databases isn't really any different than installing just one.  Are you really asking more about how to do continuous integration / continuous deployment?

Thank you for the reply!

Yeah, continues integration / development.  However, I don't need continues integration with the repository source.

I need to have a local environment for development, push changes to a staging production environment to verify no breaking changes, and a final publish to production.

hi,
I work with git repository for have three develop environmeent (if I have equal version of nop and db):
master for production, one test branch derived from master for test and after multiple dev branch I need.
by

Hello,

In short, I am looking for some guidance / best practices for such an environment with regards to the database.

- I would like to take a clone of the production database and use it for dev.
- Make various changes on the frontend, or backend within a development environment.
- Publish changes to a staging server
- Publish changes to production

Hello,

I think I got it. I am relatively new to NoP and I am taking over a production site.  As I worked through the mess.  This is what I am working with:

Using Example FQDN's:

Public Database Servers:
-Prod: mssql.example.com
-Dev: mssql-dev.example.com

Public Sites:
Prod: example.com | Prod DB
Staging: staging.example.com | Dev DB

Internal Dev:
-https://localhost:44369 | Database: localhost-docker-mssql
-https://sharedsvr.local_domain.internal | Database: mssql-dev.example.com
=================

The production store / database has several localhost / internal IP's, etc. added as multi-stores.

My question is:
Is it best practice to have production / database configured for multi-site with various localhost domains?  Or is there a better way?