CODEWITHSUNDEEP
ruby-on-railsrubyruby-on-rails-4rakecloud66
simo
simo

Reputation: 24610

rake aborted! ArgumentError: same file:

When I try to deploy my rails app at cloud66, I get this error:

rake aborted!
ArgumentError: same file: /var/deploy/website/web_head/releases/20150315170454/public/assets/tinymce/custom_content.css and /var/deploy/website/web_head/releases/20150315170454/public/assets/tinymce/custom_content.css


Tasks: TOP => assets:precompile

Can someone please explain why I get this error? how to solve it?

Upvotes: 2

Views: 1467

Answers (3)

Arpit Agarwal
Arpit Agarwal

Reputation: 527

I was facing the same problem, below steps solved it:

gem 'tinymce-rails-imageupload', github: 'PerfectlyNormal/tinymce-rails-imageupload'

Then run,

bundle install

Now check with below command:

rake assets:precompile

If the above command runs successfully with no error then it will create an assets folder in public/assets path. Delete the assets folder from 'public/assets' path.

Then git commit,push and then push to heroku. If you get the same error then add the below gem and restart again from the top.

gem "non-stupid-digest-assets"

Hope it's helpful.

Upvotes: 0

Lepage Jean Claude
Lepage Jean Claude

Reputation: 29

Never had this problem but I can see two possible causes.

First : the file is effectively required twice either directly or by different tree directives.

Second : you have a partial _custom_content and a file custom_content. Sass does not accept this configuration.

I would do a rake assets:precompile on my local machine to try to understand.

Upvotes: 0

Philip Kallberg
Philip Kallberg

Reputation: 327

How are you running your asset pre-compilation? By default, your assets will go to shared/assets on the server - are you specifying a custom location? The location is defined by config.assets.prefix.

Upvotes: 0

Related Questions