Bugzilla – Full Text Bug Listing
| Summary: | Remote SFTP folders cannot be browsed | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Mark Macdonald <mamacdon> |
| Component: | Server | Assignee: | Project Inbox <orion.server-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ahunter.eclipse |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | 416547 | ||
| Bug Blocks: | |||
This bug is similar to Bug 416547 While working on that bug I created a patch to remove the drives and add remote projects to the project list, this handles the first problem you are having. We said we would work on (2), which is the same as Bug 416547 once we added the UI for SFTP projects back in again. Sounds like everything here is covered under 416547, so closing as dupe. *** This bug has been marked as a duplicate of bug 416547 *** |
In past releases, Orion would allow you to link a remote FTP site as a top-level folder in your workspace. In 5.0 we do not have any UI for doing this. But I managed to create an SFTP folder by putting "ftp://" in my "orion.file.allowedpaths" server pref, and crafting a POST request to create a top-level folder ('project') targeting an SFTP URL: > POST http://localhost:8080/workspace/mark-OrionContent > > { > "ContentLocation": "sftp://user@ftp.example.org/whatever", > "Name": "my_ftp" > } The response indicates success: > { > "ContentLocation" : "/file/mark-OrionContent/my_ftp/", > "Id" : "my_ftp", > "Location" : "/workspace/mark-OrionContent/project/my_ftp", > "Name" : "my_ftp", > } The ContentLocation above works OK -- I can craft a URL to it, and thereby browse the SFTP folder using the folder view on the edit page. However I noticed 2 problems: 1. my_ftp is missing from the workspace's children list. So it never appears in the LHS navigator, and is impossible to access from our UI. (The server *does* list my_ftp when you GET the DriveLocation, but the client UI does not understand DriveLocations anymore, they are completely obsolete AFAIK.) 2. GETting the project Location "/workspace/mark-OrionContent/project/my_ftp" returns a bunch of nonsense (links to resources that do not exist): > { > "ContentLocation": "/workspace/mark-OrionContent/file/mark-OrionContent/my_ftp/", // what? > "Id": "my_ftp", > "Location": "/workspace/mark-OrionContent/project/my_ftp/project/my_ftp", // no > "Name": "my_ftp", > } Even if we have plans for tighter integration SFTP and Orion Projects, it seems like (1) and (2) are still bugs that should be fixed.