Upload only contents from the local folder, not the local folder with contents

[lucasmotta]

Upload only contents from the local folder, not the local folder with contents

[lucasmotta]

Yes! That's how it should work. The content inside the local path will be added to the remote path.

For example, if you have this local file tree:

- production
    - index.html
    - main.js
    - main.css

Then if you set the paths on dploy.yaml like this:

path:
    local: production/
    remote: remote_path/

Your file tree on the server will be:

- remote_path
    - index.html
    - main.js
    - main.css

[wouterds]

Hmm, the paths are set like that but they don't act like you say they should.
Maybe the include property has something to do with that..

This is my dploy.yaml file:

flyingastronauts:
 host: ******
 user: ******
 pass: ******
 scheme: sftp
 slots: 4
 include:
  "production/**": "/"
 path:
  local: production/
  remote: /public_html/beta/

(they end up like this: /public_html/beta/production/files instead of /public_html/beta/files)

[lucasmotta]

I see now... it's the current behaviour of the include parameter, but I have to change that since it's not what do you expect when setting the destination.

The only issue that I see for now, it's that you won't be able to set multiple matches in one object key, like this:

include:
  "production/** another_path/**": "/"

But I don't see a problem to ditch that, since you can still achieve the same result by creating a new key:

include:
  "production/**": "/"
  "another_path/**": "/"

I will work on this now and release a new version in a bit.

[wouterds]

Awesome!

[lucasmotta]

Version 1.0.3 should fix this. Let me know if it works.

[lucasmotta]

Oh, and just to make sure, set the flag check to true, so you can see where your files will be uploaded, before actually uploading it. It's easier to test like this.

[wouterds]

Whenever I run dploy (installed from the git repo) I get these errors: .

When I just run sudo npm install dploy -g it still installs V1.0.1

[wouterds]

Update: Nvm @ above. Installed 1.0.4 like this sudo npm install dploy -g but I still get the same errors.

module.js:340
    throw err;
          ^
Error: Cannot find module '/usr/local/lib/node_modules/dploy/lib/dploy.js'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/usr/local/lib/node_modules/dploy/bin/dploy:5:6)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)

[lucasmotta]

It looks like you downloaded DPLOY, but you haven't compiled the CoffeeScript. That's an easy fix, just go to your DPLOY repo and run:

grunt && grunt watch

There's a small note about this on the README file:
https://github.com/LeanMeanFightingMachine/dploy/#contribute

But probably your fork is not the latest one, so I suggest you merging my latest updates first. Let me know how it goes!

[wouterds]

Hmm, I can't remember I did that the first time I used dploy this morning.
I just ran sudo npm install dploy and it just worked.

Now I removed it, installed it the same way as this morning but now I get this error.
But this should fix it: cd to /usr/local/lib/node_modules/dploy and run grunt & grunt watch?

[lucasmotta]

That's weird... Have you tried to uninstall and install it again?
If still doesn't work, try what you suggested above, but it's definitely not a solution :(

[wouterds]

Reinstalled it again, now it get a little further.
After confirming the files however I get this:

[ + ] Fail uploading file production: { [Error: Failure] lang: '' }
[ + ] Fail uploading file production: { [Error: Failure] lang: '' }
[ + ] Fail uploading file production: { [Error: Failure] lang: '' }
[ + ] Fail uploading file production: { [Error: Failure] lang: '' }
[ + ] Fail uploading file production: { [Error: Failure] lang: '' }
[ + ] Fail uploading file production: { [Error: Failure] lang: '' }
[ + ] Fail uploading file production: { [Error: Failure] lang: '' }
[ + ] Fail uploading file production: { [Error: Failure] lang: '' }
[ + ] Fail uploading file production: { [Error: Failure] lang: '' }
[ + ] Fail uploading file production: { [Error: Failure] lang: '' }
[ + ] Fail uploading file production: { [Error: Failure] lang: '' }

[wouterds]

Any idea how I solve this issue? Is it a bug or did I do something wrong?

[lucasmotta]

I finally managed to replicate this bug! Hold on tight, I will fix this!

[wouterds]

Hehe, ok :)!

[lucasmotta]

Try now in the version 1.0.7.
The problem was that node-glob was matching folders and files. So I just had to create a filter to match only files, since the folders are created recursively by DPLOY.

[wouterds]

Works perfect now, really a tool that I've been waiting for.
Thanks man, I love it!