tag:help.appveyor.com,2012-11-13:/discussions/problems/1143-problems-with-artifact-folder-structure-in-vanilla-ftp-deploymentAppVeyor: Discussion 2015-06-11T19:34:01Ztag:help.appveyor.com,2012-11-13:Comment/354383712014-12-02T16:53:01Z2015-03-31T05:39:35ZProblems with artifact folder structure in vanilla FTP deployment<div><p>Hi guys,</p>
<p>I'm trying to set up a build for a vanilla HTML site via FTP,
for some simple UX staging.<br>
I've disabled build, so that the process just checks out the files
and moves straight to the artifacts step.<br>
In the repo, I keep the site source in a 'src' folder, which is the
root of the site.<br>
I add src*** as an artifact to capture all files in the 'src'
folder.<br>
When I try to deploy via FTP, it's attempting to deploy (for
example) to ROOT\src\index.html, instead of ROOT\index.html.<br>
Is there a way to tell the FTP deployment to upload files from a
certain artifact subpath? Or map the artifacts into another
path?<br>
In TeamCity you can do something like src*** => ***.</p></div>sebastiantag:help.appveyor.com,2012-11-13:Comment/354383712014-12-02T19:40:09Z2014-12-02T19:40:09ZProblems with artifact folder structure in vanilla FTP deployment<div><p>First, you should have a single <code>.zip</code> artifact. To
upload entire folder as a single zip remove <code>\**\*</code> from
artifact path.</p>
<p>Then use <code>Application</code> field to specify zip artifact
name to make AppVeyor "expanding" it before publishing to FTP.</p>
<p>Let me know how it goes.</p></div>Feodor Fitsner