You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected Behavior
I want to deploy from Windows to a UNIX system using the same files I would use if I ran hapistrano from Linux.
Actual Behavior
I'm getting this error when deploying from Windows.
> hap deploy -c deploy/staging.yaml…Aeson exception:…Error in $['deploy_path']: InvalidAbsDir "/var/www/staging"…
Other details
Hapistrano uses the path library. path has support for windows. However, pathmakes a distinction to expose certain behavior according to the system it is being compiled on:
{-# LANGUAGE CPP #-}
#if defined(mingw32_HOST_OS)
modulePath(modulePath.Windows) whereimportPath.Windows#elsemodulePath(modulePath.Posix) whereimportPath.Posix#endif
That means that if hapistrano is compiled on Windows, it will validate that all paths on the server.yml files have valid deployment paths. If the target is Unix, the path will still appear as invalid since path's validation relies on the system it was compiled on.
The text was updated successfully, but these errors were encountered:
I'm going to close this issue for now since it was labeled as wontfix. We can reopen it in the feature since no one else has requested to take a look at it.
Expected Behavior
I want to deploy from Windows to a UNIX system using the same files I would use if I ran hapistrano from Linux.
Actual Behavior
I'm getting this error when deploying from Windows.
Other details
Hapistrano uses the
path
library.path
has support for windows. However,path
makes a distinction to expose certain behavior according to the system it is being compiled on:That means that if hapistrano is compiled on Windows, it will validate that all paths on the
server.yml
files have valid deployment paths. If the target is Unix, the path will still appear as invalid sincepath
's validation relies on the system it was compiled on.The text was updated successfully, but these errors were encountered: