Strategy for deploying from build directory without tracking it

[MarkLeMerise]

Right now, I have a pretty basic folder structure for my app:

| myapp
    |--www
    |--deploy
    |--dploy.yaml
    |--buildfile

When I run a build process, it builds into the deploy folder, which I have also set in .gitignore. I have added www to the exclude array in dploy.yaml.

With this setup, DPLOY will only want to upload the .rev file and nothing else. Ideally, I would like to keep the deploy directory ignored as it adds a lot of weight to the repo if tracked. Is there a prescribed strategy for this type of situation?

[lucasmotta]

Hey @mslemeri.. I've been discussing this for a while, but it's a tricky issue. Basically it's because we use git to track the files that were changed, and if they are not tracked we cannot know which files to upload.
We may implement in the future a simple modified-date kind of tracking, but it's not on our priority at the moment - but if anyone wants to give it a try, would be awesome.
You can read a bit more at #15.

[yahreen]

Is it considered best practice to include the .rev file with your repo? Or should we .gitignore it?

[mattfelten]

I would second this. I've been doing a lot more Jekyll websites recently and have to check in the compiled site and have Dploy exclude everything but the build dir. It's a little janky.

[baires]

👍

[lucasmotta]

I'm happy to say that the new dploy will have a new map parameter, which will allow you to upload the files that are not being tracked by Git!
Have a look at this discussion: #72 - the new version of dploy will be pushed to npm at some point next week!