-
Notifications
You must be signed in to change notification settings - Fork 57
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
Multiple Paths #95
Comments
You might want to look into using Ansible in combination with dandelion. I'm deploying to multiple servers and directories on the same server with one config file per directory. It's definitely not DRY, but it works until something can be built. |
What about a config option where you specify some sort of path mapping? For example, in the case presented above something like: path_map:
- public_html/folder2: folder2 Would something like this work for you? I'm not thrilled with the name |
Hi scttnlsn. I think this would be a great solution and path_map name seems to fit well for this option. A small doubt in this case would be transferred to folder2 only place that I specify, ignoring the original path? If it works that way I think would be the perfect solution. |
@samgavinio Yeah, this issue is still open. #61 is a subset of this issue since it refers specifically to the |
Dandelion met recently and quite liked it.
However after some time using I thought it would be possible to use multiple paths, I may be talking nonsense, but what do you think of the idea below?
I have the following site structure
app/
folder1/
public_html/folder2/
But on the server I would like to stay
app/
folder1/
folder2/
I know of to include additional folders informing the way, are always put these folders are sent, regardless of whether or not changes have been made.
Would not be possible to inform different paths so that whenever a change is made in the folder folder2 changes to it are referred to public_html/folder2 sent folder?
Not forgetting thank me for this excellent tool, was one of the best options I found.
The text was updated successfully, but these errors were encountered: