Configurer l'accélération SSL avec HTTP sur le front et SSL sur le back-end
| Entité | Nom | Valeur |
|---|---|---|
| Service SSL | Service-SSL-1 | 10.102.20.30 |
| Service-SSL-2 | 10.102.20.31 | |
| Serveur virtuel basé sur HTTP | Vserver-HTTP-1 | 10.102.10.20 |
Something went wrong opening the GitHub link. Please try again.
| Entité | Nom | Valeur |
|---|---|---|
| Service SSL | Service-SSL-1 | 10.102.20.30 |
| Service-SSL-2 | 10.102.20.31 | |
| Serveur virtuel basé sur HTTP | Vserver-HTTP-1 | 10.102.10.20 |
Commit Guidelines
Before we start looking at the specific use cases, here’s a quick note about commit messages. Having a good guideline for creating commits and sticking to it makes working with Git and collaborating with others a lot easier. The Git project provides a document that lays out a number of good tips for creating commits from which to submit patches — you can read it in the Git source code in the Documentation/SubmittingPatches file.
Private Small Team
The simplest setup you’re likely to encounter is a private project with one or two other developers. “Private,” in this context, means closed-source — not accessible to the outside world. You and the other developers all have push access to the repository.
Something went wrong opening the GitHub link. Please try again.