nimdraug/taters

A fully modular build and deployment framework

taters's Issues

unicode filenames and ftp locations

Seems like there is an issue putting files w/ unicode filenames into ftp locations. Needs further testing along with other location types.

Locations should not accept absolute paths

Currently any location is okay with getting files with absolute paths, meaning that files can be put outside of the location, potentially leading to issues.
If a file is inadvertently passed with an absolute path, it should be applied as if it's relative to the location's base path.

ftp location source does not return correct paths

taters.locations.ftp( 'ftp://a.com/x/y' ).source() yields files with their dirname set to /x/y (as in /x/y/somefile.txt), which when passed to a local location will attempt to create that path, causing a permission error.

Additionally, local locs should not accept absolute paths in the first place, and always assume they are relative to the local loc's basepath. Fixing this would also resolve this issue.