Skip to content
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.

Stage content on a remote machine #44

Open
gtkramer opened this issue Oct 16, 2019 · 1 comment
Open

Stage content on a remote machine #44

gtkramer opened this issue Oct 16, 2019 · 1 comment

Comments

@gtkramer
Copy link
Contributor

Content needs to be able to be staged on a remote machine. Rather than just moving content into a new location, it should be rsync'd to a path. This path may be local, or it may be another machine. This allows for more complex infrastructure setups and requirements when dealing with larger amounts of data that need mirrored as a part of the publishing process.

@mbelluzzo mbelluzzo added this to the Up-to-pair milestone Oct 31, 2019
@mbelluzzo mbelluzzo modified the milestones: Up-to-pair, Future Dec 7, 2019
@mbelluzzo
Copy link
Contributor

Having the staging folder to be a nfs mount is a very easy way of accomplish this. And we do depend a lot on the staging dir being local. So it would be a somewhat big change to get marginal flexibility at the moment.

So I would say that this is nice but low priority atm.

@gtkramer gtkramer removed this from the Future milestone Dec 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants