9
votes
How to synchronize deployments (especially of database object changes) on multiple environments
I would integrate the schema management into the application itself (or along with it).
Any change to the schema should be committed along the application code (and hence tagged also).
There's ...
6
votes
Accepted
Deploying VMs using roles and hosts in Ansible based on operating system
So I managed to keep the same structure roughly, and managed to separate how the machines are generated, however still is a bit fuzzy and can probably be improved to be more efficient!
site.yml
- ...
5
votes
How to reconcile Infrastructure as Code and not storing env config in code?
There are, as always, a few ways to solve this.
You can use a central source to keep secrets that each server reads from ala Hashicorp Vault. While popular this is not my preferred approach as its ...
4
votes
How to synchronize deployments (especially of database object changes) on multiple environments
In our company we manage our application code within a VCS (Git) and most of the applications we work with install their core database from within the setup scripts that ship with the application.
If ...
4
votes
Accepted
What approach should I take to store environment variables for a repo?
General Notes
I don't really understand this one:
However, this seems clunky, as I have to create the logic to read this
file in every script that is made.
You can source all variables from a ...
3
votes
Accepted
Build Docker Images with Ansible + Vagrant
If it's within scope, I would use Packer to build the artifacts.
Write a Packer template using the builders that you want:
Vagrant builder for the Vagrant image
Docker builder for the Docker image.
...
3
votes
Growing local development environment issues
I recommend running all the dependent microservices on cloud and deploy only the microservice that is under active development in your laptop.
3
votes
How to approach dynamic environments per Git feature branch workflow?
What you're after is referred to as "Review Apps" by Gitlab and Heroku. It relies on a CI/CD system that runs pipelines on every branch, and exposes the branch name to the build (usually as an ...
3
votes
Accepted
How does 'Environment Management' work in a DevOps world?
I've never heard of an "Environment Manager." Release Management, on the other hand, has historically been consolidated to a single person or team.
In a DevOps model, Release Management is more of ...
3
votes
Accepted
VM Hosts: Single Large Host or Few Smaller Hosts?
A good rule of thumb is to try and avoid using one bit of logical kit (be it a single VM or a single physical host) for more than one thing.
If a physical server is going to be a VM host then that's ...
2
votes
How to reconcile Infrastructure as Code and not storing env config in code?
This is a common problem in configuration management, and while I can't speak for Chef as I haven't worked with it, I can tell you how this is solved by both Puppet and SaltStack.
Firstly, this ...
2
votes
Accepted
What's the best way to restrict an environment to a specific CDN?
If the different CDNs are hosted at different IP addresses one possibility might be to configure the local hosts table for the machines in a certain environment in such way as to overwrite the DNS ...
2
votes
Should I shut down the staging environment when the deployment test ends?
How big is the app? How much usage will it get in staging?
If you spin it up on a t2.micro, the extra cost will be negligible, especially if you use auto-shutdown or Terraform to only have the box ...
2
votes
Should I shut down the staging environment when the deployment test ends?
You can approach this case with multiple ways.
For example you can set an auto-shutdown for 20:00 pm and auto-start for 8:00 am.
Use Terraform to create your environment and, after deployment/...
1
vote
How many deployment environments are appropriate for SPA + API architecture?
My first thought when I see two components that depend on each other during a deployment - often the app and the database - I try to come up with a way to decouple them.
If you can deploy your UI and ...
1
vote
Accepted
How to put production-like data into version control
it depends a bit what kind of cms you use, most cms offer a way to package data in to packages that you can check in to git and deploy to databases almost like code to webapps.
For example, we work ...
1
vote
Growing local development environment issues
There are several options for handling this and they are not exclusive of each other:
Giving your developers machines with lots of memory and CPU, and probably GPU, is a quick way to solve problems ...
1
vote
Accepted
Preventing accidental production deployments in ansible
The best practice is to separate production and staging(testing) inventory. See Staging vs Production.
This way you pick with -i what you are targeting.
To make it more robust you might want to ...
1
vote
Should I shut down the staging environment when the deployment test ends?
It's better to create a new instance for staging, deploy the app, test it, stop the instance when you finish testing.
1
vote
Best Practice for Kubernetes Development Environment
It's really up to your personal preference, but for minikube you can certainly follow the same standards that you would for production.
If your production environment will use some sort of volume ...
1
vote
What are the cost effective ways to deploy services using Kubernetes on multiple deployment environments?
Based on my experience I'd suggest following scenario:
First you should make your apps deployment process similar for all environments, so same tool and set of files will be responsible for this part. ...
1
vote
Accepted
How to handle resource creation?
You can use Terraform for azure to handle the dynamic creation of azure resources in the release pipeline in Azure DevOps. Terraform maintains a state file for all the created resources after a run.
...
1
vote
Accepted
How to manage images versions via docker-compose with Ansible
The best way is of course (like Zeitounator comments) to use a inventory var. Either you use the version number in the docker-compose task as a variable or you create a Jinja2 template docker-compose....
1
vote
GUI over GitLab CI Environment Deployments With Multiple Instances?
Check out the GitLab Operations Dashboard feature (https://docs.gitlab.com/ee/user/operations_dashboard/)
There is a screenshot on that page, too, so you can get an idea of it.
1
vote
Accepted
How to setup multiple build environments in Azure DevOps/TFS2018?
This is a general issue with react apps that is independent of what CI/CD stack you use that is discussed at https://stackoverflow.com/questions/49975735/rendering-an-environment-variable-to-the-...
1
vote
Deploying VMs using roles and hosts in Ansible based on operating system
https://github.com/030/ansible-certbot
main.yml
- include: Debian.yml
when: ansible_os_family == 'Debian'
put everything that is required on debian like apt in Debian.yml and yum in Centos.yml.
In ...
1
vote
VM Hosts: Single Large Host or Few Smaller Hosts?
As I see it, the basic problem you have is that you aren't looking at the Total Cost of Ownership (TCO). While you may eventually save on the hardware costs, this is costing you in man-hours - either ...
1
vote
Where to Store Container Configuration
we do this with .conf files and loading them via compose
env_file: /path/to/our.conf
they can also be used with
docker run --env-file /path/to/our.conf ourcontainer:version
In some cases we use ...
1
vote
How does 'Environment Management' work in a DevOps world?
I see three way to handle this need.
The software declare its dependencies and is released with each dependency at the correct version independently of others. This may create problems if two version ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
environments × 25deployment × 8
docker × 4
ansible × 4
kubernetes × 3
environment-variables × 3
versioning × 3
azure-devops × 2
azure × 2
continuous-delivery × 2
infrastructure-as-code × 2
servers × 2
tfs × 2
amazon-web-services × 1
continuous-integration × 1
terraform × 1
docker-compose × 1
containers × 1
git × 1
gitlab × 1
amazon-ec2 × 1
continuous-deployment × 1
windows × 1
culture × 1
azure-pipelines × 1