Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skipping asset precompilation: wrong copy paths #246

Closed
zhulik opened this issue Oct 27, 2014 · 2 comments
Closed

Skipping asset precompilation: wrong copy paths #246

zhulik opened this issue Oct 27, 2014 · 2 comments

Comments

@zhulik
Copy link

zhulik commented Oct 27, 2014

When mina skipping assets precompilation it trying to execute

#{echo_cmd %[cp -R "#{deploy_to}/#{current_path}/public/assets" "./public"]}

So, on my server "#{deploy_to}/#{current_path}/public/assets" and "./public" is the same folders. Is it my mistake or mina bug?

My deploy log:

...
It was installed into ./vendor/bundle
-----> DB migrations unchanged; skipping DB migration
-----> Skipping asset precompilation
cp: `/home/deployer/lifescan/current/public/assets' and `./public/assets' are the same file
! ERROR: Deploy failed.
-----> Cleaning up build
Unlinking current
OK
@gabskoro
Copy link
Member

Hi @zhulik you are using the wrong version od mina :), have you updated it globally? (gem install mina), because as far as I can see you wrote this line

#{echo_cmd %[cp -R "#{deploy_to}/#{current_path}/public/assets" "./public"]}

And this is being executed

#{echo_cmd %[cp -R "#{deploy_to}/#{current_path}/public/assets" "./public/assets"]}

note the "/assets" at the end.

@d4be4st
Copy link
Member

d4be4st commented Jan 22, 2015

3 months passed, closing issue

@d4be4st d4be4st closed this as completed Jan 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants