Skip to content

Use ip's for production hosts when creating dump and syncing #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Qwinci
Copy link
Contributor

@Qwinci Qwinci commented Mar 14, 2025

Use production host from the inventory with a different hostname
<hostname>.prod when creating the dump and syncing to avoid dns/Ansible
issues where the dump would be created on the target machine instead of the
production machine. This requires that the production ip's are specified
in the inventory under the .prod hostname with ansible_host and possibly
the user with ansible_user if running against Vagrant VM where the used user
doesn't match the one used on the production machine.
This should be merged at around the same time with the corresponding file sync change and possibly inventory changes.

@ajsalminen
Copy link
Member

So with doppelgaenger this would mean the production hosts just get added in the inventory with the .prod suffix in the inventory script instead of as is?

When setting up a new server that will replace the prod you'd change the IP for the production server's name and add a '.prod' into the inventory for syncing?

What about syncing to a clone of a production server that does not have the same hostname, a staging instance or such?

I think it will be good to document how to use this once the details are finalized.

Use production host from the inventory with a different hostname
`<hostname>.prod` when creating the dump and syncing to avoid dns/Ansible
issues where the dump would be created on the target machine instead of the
production machine. This requires that the production ip's are specified
in the inventory under the .prod hostname with `ansible_host` and possibly
the user with `ansible_user` if running against Vagrant VM where the used user
doesn't match the one used on the production machine.
@Qwinci Qwinci force-pushed the use-ips-for-prod-hosts branch from d9b940e to 79883ce Compare April 16, 2025 06:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants