Closed alexelash closed 8 years ago
I believe dandelion init <revision>
is what you're looking for. This will simply write the given revision SHA into the remote .revision
file.
The revision_file
configuration option is to specify the remote revision filename (the default is .revision
).
Hope that helps!
Thank you so much! This is extremely helpful.
Hi,
I'm actually moving from Springloops.io to using Bitbucket. I've moved a project (that was already deployed to the Live server) to Bitbucket, and would now like to test deploying using Dandelion.
My question is: is there a way (as on Springloops, screenshot attached):
to put in the Dandelion.yml file that this is not the first deployment? When I ran a dry run, of course Dandelion showed that it would put up allllll of the files in my most recent revision. Is the below (from the docs) what I need to use?
Thanks! Sorry for the likely n00b question.