{"_id":"5637e0c3fbe1c50d008cb06a","version":{"_id":"55faf11ba62ba1170021a9aa","project":"55faf11ba62ba1170021a9a7","__v":40,"createdAt":"2015-09-17T16:58:03.490Z","releaseDate":"2015-09-17T16:58:03.490Z","categories":["55faf11ca62ba1170021a9ab","55faf8f4d0e22017005b8272","55faf91aa62ba1170021a9b5","55faf929a8a7770d00c2c0bd","55faf932a8a7770d00c2c0bf","55faf94b17b9d00d00969f47","55faf958d0e22017005b8274","55faf95fa8a7770d00c2c0c0","55faf96917b9d00d00969f48","55faf970a8a7770d00c2c0c1","55faf98c825d5f19001fa3a6","55faf99aa62ba1170021a9b8","55faf99fa62ba1170021a9b9","55faf9aa17b9d00d00969f49","55faf9b6a8a7770d00c2c0c3","55faf9bda62ba1170021a9ba","5604570090ee490d00440551","5637e8b2fbe1c50d008cb078","5649bb624fa1460d00780add","5671974d1b6b730d008b4823","5671979d60c8e70d006c9760","568e8eef70ca1f0d0035808e","56d0a2081ecc471500f1795e","56d4a0adde40c70b00823ea3","56d96b03dd90610b00270849","56fbb83d8f21c817002af880","573c811bee2b3b2200422be1","576bc92afb62dd20001cda85","5771811e27a5c20e00030dcd","5785191af3a10c0e009b75b0","57bdf84d5d48411900cd8dc0","57ff5c5dc135231700aed806","5804caf792398f0f00e77521","58458b4fba4f1c0f009692bb","586d3c287c6b5b2300c05055","58ef66d88646742f009a0216","58f5d52d7891630f00fe4e77","59a555bccdbd85001bfb1442","5a2a81f688574d001e9934f5","5b080c8d7833b20003ddbb6f"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"55faf932a8a7770d00c2c0bf","pages":["56268a69b1c2630d00b112b0","56268a85c2781f0d00364bbc","56268a92c2781f0d00364bbe","5637e0a0cfaa870d00cdeb6a","5637e0c3fbe1c50d008cb06a","5637e164f7e3990d007b2c41"],"version":"55faf11ba62ba1170021a9aa","__v":6,"project":"55faf11ba62ba1170021a9a7","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-17T17:32:34.286Z","from_sync":false,"order":8,"slug":"bring-your-private-data","title":"BRING YOUR PRIVATE DATA"},"parentDoc":null,"__v":15,"githubsync":"","project":"55faf11ba62ba1170021a9a7","user":"554340dfb7f4540d00fcef1d","updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-11-02T22:16:35.232Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"To copy files over from a public or private FTP or HTTP(S) server, use the FTP/HTTP(S) import tool. It runs in the background on the CGC and does not depend on your local network speed. This allows you to multitask as your files are added to your project.\n\nTo import files from an FTP or HTTP(S) server:\n\n1. [Navigate to the desired project](doc:view-a-project). \n2. Go to the **Files** tab in the project and click the **+ Add Files** button.\n2. Click **FTP/HTTP**, as shown below.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/f04ebcf-cgc-import-from-an-ftp-http-server-1.png\",\n        \"cgc-import-from-an-ftp-http-server-1.png\",\n        914,\n        687,\n        \"#e6eced\"\n      ],\n      \"border\": true\n    }\n  ]\n}\n[/block]\n3. Type in or paste the URL of the file(s) you want to import. Or, click **Browse** to navigate to a text file on your computer that contains these URLs.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"You can upload a single file, a directory (in the case of FTP), or an index page (in the case of HTTP(S)).\\n\\nYou can also upload a list of URLs. They will all be uploaded in the same job.\",\n  \"title\": \"Types of uploads\"\n}\n[/block]\n4. *Optional:* Enter tags in the **Tag files** box. This makes it easier to visually identify and organize files. Separate tags with commas or by hitting the return key. All tags which are already in the selected project are autosuggested in the drop-down menu. Learn more about [tagging your files](tag-your-files).\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Tagging files\",\n  \"body\": \"You can also tag files as you upload them [via the CGC Uploader](upload-via-the-cgc-uploader) or [via the command line](upload-via-the-command-line).\"\n}\n[/block]\n6. **Resolve naming conflicts** - Select the action to be taken if a naming conflict occurs. Available actions are **Skip** (default option), **Auto-rename** and **Overwrite**. Read more about naming conflicts resolution [below](#section-resolving-naming-conflicts).\n7. **Preserve folder structure** - If enabled, the imported items will be an exact mirror of the file/folder structure on the server. Otherwise, the items will be \"flattened\" when imported from the server, i.e. only files will be imported, with no folder structure.\n8. Click **Import** to start the upload.\n9. Click **Import more files** if you have more URLs to import. If you're finished uploading, click **Done** to close the dialog.\n[block:callout]\n{\n  \"type\": \"success\",\n  \"body\": \"You can track the import progress under the import status icon on the right-hand side of the main menu.\",\n  \"title\": \"Track your progress\"\n}\n[/block]\n\nWhen the upload completes, review your files in the **Files** tab of the project.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"Note that currently tags added to a file can only be viewed via the CGC visual interface. We are working to make these tags available via the API.\"\n}\n[/block]\n<div align=\"right\"><a href=\"#top\">top</a></div>\n\n##Accessing password-protected FTP and HTTP(S) servers\n\nThe FTP/HTTP(S) tool can submit usernames and passwords to the server. To do this, you should include the username and password in the links that you pass to the tool, using the standard HTTP syntax: `http://username:password:::at:::example.org/sample/`.\n\nPasting in a link formatted in this way will attempt to authenticate with the server `example.org` using the credentials `username` and `password` and then try to fetch everything that is hosted under the `directory/sample/`.\n\n## RESOLVING NAMING CONFLICTS\n\nNaming conflicts happen when you try to import an item (file or folder) from an FTP/HTTP server to a project's root folder or subfolder, where an item with the same name already exists. The list below illustrates the possible cases of naming conflicts and the way they are resolved depending on which option is selected in the **Resolve naming conflicts** dropdown:\n\n1. Importing a **file** that has the same name as an existing **file** at the destination path:\n    * **Skip** (default): The file won't be imported. This is the default behavior.\n    * **Auto-rename**: The imported file will be automatically renamed by adding a prefix (underscore and serial number).\n    * **Overwrite**: The existing file will be overwritten by the file imported from the server.\n2. Importing a **file** that has the same name as an existing **folder** at the destination path:\n    * **Skip** (default): The file won't be imported.\n    * **Auto-rename**: The imported file will be automatically renamed by adding a prefix (underscore and serial number).\n    * **Overwrite**: The file won't be imported.\n3. Importing a **folder** that has the same name as an existing **folder** at the destination path:\n    * The content of the folder that is being imported will be merged with the content of the existing folder, regardless of the option selected in the **Resolve naming conflicts** dropdown. Any conflicts related to files within the folders will be handled according to file naming conflict resolution rules described above.\n4. Importing a **folder** that has the same name as an existing **file** at the destination path:\n    * The folder and the files it contains won't be imported. This is the default, non-configurable behavior, regardless of the option selected in the **Resolve naming conflicts** dropdown.\n\nThe following table illustrates the entire naming conflict resolution mechanism:\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/763fd8b-conflict-resolution-matrix.png\",\n        \"conflict-resolution-matrix.png\",\n        471,\n        296,\n        \"#f1f1f1\"\n      ]\n    }\n  ]\n}\n[/block]\n##Troubleshooting\nIf the Seven Bridges FTP import tool fails to import all the files whose links you provided, please retry by providing shorter lists of FTP links.\n\n\n<div align=\"right\"><a href=\"#top\">top</a></div>","excerpt":"<a name=\"top\"></a>","slug":"upload-from-an-ftp-server","type":"basic","title":"Import from an FTP or HTTP(S) server"}

Import from an FTP or HTTP(S) server

<a name="top"></a>

To copy files over from a public or private FTP or HTTP(S) server, use the FTP/HTTP(S) import tool. It runs in the background on the CGC and does not depend on your local network speed. This allows you to multitask as your files are added to your project. To import files from an FTP or HTTP(S) server: 1. [Navigate to the desired project](doc:view-a-project). 2. Go to the **Files** tab in the project and click the **+ Add Files** button. 2. Click **FTP/HTTP**, as shown below. [block:image] { "images": [ { "image": [ "https://files.readme.io/f04ebcf-cgc-import-from-an-ftp-http-server-1.png", "cgc-import-from-an-ftp-http-server-1.png", 914, 687, "#e6eced" ], "border": true } ] } [/block] 3. Type in or paste the URL of the file(s) you want to import. Or, click **Browse** to navigate to a text file on your computer that contains these URLs. [block:callout] { "type": "info", "body": "You can upload a single file, a directory (in the case of FTP), or an index page (in the case of HTTP(S)).\n\nYou can also upload a list of URLs. They will all be uploaded in the same job.", "title": "Types of uploads" } [/block] 4. *Optional:* Enter tags in the **Tag files** box. This makes it easier to visually identify and organize files. Separate tags with commas or by hitting the return key. All tags which are already in the selected project are autosuggested in the drop-down menu. Learn more about [tagging your files](tag-your-files). [block:callout] { "type": "success", "title": "Tagging files", "body": "You can also tag files as you upload them [via the CGC Uploader](upload-via-the-cgc-uploader) or [via the command line](upload-via-the-command-line)." } [/block] 6. **Resolve naming conflicts** - Select the action to be taken if a naming conflict occurs. Available actions are **Skip** (default option), **Auto-rename** and **Overwrite**. Read more about naming conflicts resolution [below](#section-resolving-naming-conflicts). 7. **Preserve folder structure** - If enabled, the imported items will be an exact mirror of the file/folder structure on the server. Otherwise, the items will be "flattened" when imported from the server, i.e. only files will be imported, with no folder structure. 8. Click **Import** to start the upload. 9. Click **Import more files** if you have more URLs to import. If you're finished uploading, click **Done** to close the dialog. [block:callout] { "type": "success", "body": "You can track the import progress under the import status icon on the right-hand side of the main menu.", "title": "Track your progress" } [/block] When the upload completes, review your files in the **Files** tab of the project. [block:callout] { "type": "info", "body": "Note that currently tags added to a file can only be viewed via the CGC visual interface. We are working to make these tags available via the API." } [/block] <div align="right"><a href="#top">top</a></div> ##Accessing password-protected FTP and HTTP(S) servers The FTP/HTTP(S) tool can submit usernames and passwords to the server. To do this, you should include the username and password in the links that you pass to the tool, using the standard HTTP syntax: `http://username:password@example.org/sample/`. Pasting in a link formatted in this way will attempt to authenticate with the server `example.org` using the credentials `username` and `password` and then try to fetch everything that is hosted under the `directory/sample/`. ## RESOLVING NAMING CONFLICTS Naming conflicts happen when you try to import an item (file or folder) from an FTP/HTTP server to a project's root folder or subfolder, where an item with the same name already exists. The list below illustrates the possible cases of naming conflicts and the way they are resolved depending on which option is selected in the **Resolve naming conflicts** dropdown: 1. Importing a **file** that has the same name as an existing **file** at the destination path: * **Skip** (default): The file won't be imported. This is the default behavior. * **Auto-rename**: The imported file will be automatically renamed by adding a prefix (underscore and serial number). * **Overwrite**: The existing file will be overwritten by the file imported from the server. 2. Importing a **file** that has the same name as an existing **folder** at the destination path: * **Skip** (default): The file won't be imported. * **Auto-rename**: The imported file will be automatically renamed by adding a prefix (underscore and serial number). * **Overwrite**: The file won't be imported. 3. Importing a **folder** that has the same name as an existing **folder** at the destination path: * The content of the folder that is being imported will be merged with the content of the existing folder, regardless of the option selected in the **Resolve naming conflicts** dropdown. Any conflicts related to files within the folders will be handled according to file naming conflict resolution rules described above. 4. Importing a **folder** that has the same name as an existing **file** at the destination path: * The folder and the files it contains won't be imported. This is the default, non-configurable behavior, regardless of the option selected in the **Resolve naming conflicts** dropdown. The following table illustrates the entire naming conflict resolution mechanism: [block:image] { "images": [ { "image": [ "https://files.readme.io/763fd8b-conflict-resolution-matrix.png", "conflict-resolution-matrix.png", 471, 296, "#f1f1f1" ] } ] } [/block] ##Troubleshooting If the Seven Bridges FTP import tool fails to import all the files whose links you provided, please retry by providing shorter lists of FTP links. <div align="right"><a href="#top">top</a></div>