I haven't, but a generic pattern that works in this situation is to have two projects; one for the droplet + contents, and one for everything outside it. StackReferences to share data. That way, you can safely destroy / up the droplet stack on every deploy.