Answers: <p>If by "Shared" you mean that your team has access to the files then it should be stored in Source Control so that everyone on the team is using the same scripts.  You can consider a secrets manager so that team members do not share sensitive information (e.g., <a href="https://docs.docker.com/engine/swarm/secrets/" rel="nofollow noreferrer">Docker Secrets</a>, <a href="https://aws.amazon.com/blogs/aws/aws-secrets-manager-store-distribute-and-rotate-credentials-securely/" rel="nofollow noreferrer">AWS Secrets Manager</a>, <a href="https://azure.microsoft.com/en-us/services/key-vault/" rel="nofollow noreferrer">Azure Key Vault</a>).</p>
  
  <p>If this will be publicly available you can still use a secrets manager to publish these files with the sensitive data removed.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-02-24T22:47:49.207Z
Answers: It will be shared with different clients
Answers: irbian
Answers: CC BY-SA 4.0
Answers: 2020-02-24T16:37:21.063Z
Answers: 2020-02-24T16:37:21.063Z
Answers: Wesley Rolnick
Body: <p>Let´s suppose that our repository contents is something that will be shared. Is strange that we include the deploy scripts there, explaining how to deploy in our machines</p>
  
Tags: <configuration-management>
Title: Where do you store your configurations? Dockerfiles, gitlab-ci, application.properties, deploy scripts
UserDisplayName: irbian
ThreadText: # Where do you store your configurations? Dockerfiles, gitlab-ci, application.properties, deploy scripts
  
  (Asked by: username_0 on 2020-02-24)
  
  Let´s suppose that our repository contents is something that will be shared. Is strange that we include the deploy scripts there, explaining how to deploy in our machines
  
  **Tags:** configuration-management
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-02-24. Score: 1
  
  If by "Shared" you mean that your team has access to the files then it should be stored in Source Control so that everyone on the team is using the same scripts. You can consider a secrets manager so that team members do not share sensitive information (e.g., [Docker Secrets](https://docs.docker.com/engine/swarm/secrets/), [AWS Secrets Manager](https://aws.amazon.com/blogs/aws/aws-secrets-manager-store-distribute-and-rotate-credentials-securely/), [Azure Key Vault](https://azure.microsoft.com/en-us/services/key-vault/)).
  
  If this will be publicly available you can still use a secrets manager to publish these files with the sensitive data removed.
  
  > **Comments:**
  > **username_0**: It will be shared with different clients  
  
  ---
  
  