Pages target dir

[adrianbroher]

This PR tries to take a stab at #1164.

Never did anything related to ruby, so feedback is appreciated.

[svenfuchs]

this looks quite good to me @adrianbroher! i am wondering if the log output will be very useful if we omit the work dir from it, and i'm not sure we need the dst_dir method at all if it's just eqal to target_dir, but those are rather cosmetic questions.

have you been able to test this with an actual deployment?

you can trigger a deployment with your fork like so:

deploy:
- provider: pages
  edge: 
    repo:  adrianbroher/dpl
    branch: pages-target-dir
    # ...

[svenfuchs]

i think this can just be target_dir, in which case we wouldn't need the extra method dst_dir below.

[adrianbroher]

am wondering if the log output will be very useful if we omit the work dir from it

I can add another message to the setup method.

and i'm not sure we need the dst_dir method at all if it's just eqal to target_dir

I actually wanted to add a guard/limitation so that target_dir can only be a descendant directory of work_dir. However I have yet to find out how to implement this in ruby and if the accessor is the right place for this or if this opt thing allows validators.

have you been able to test this with an actual deployment?

No, but I created this test repository.

• The .travis.yml configuration.
• The gh-pages deployment branch (only subdir is populated via dpl, the root is manually maintained).
• The working build
• The actual deployment

[adrianbroher]

While looking at the log of the build it may be a good idea to call git add -A %{dst_dir} instead of git add -A ..