Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Deployment fails for Rails App with App Platform - No such file or directory - /workspace/node_modules/.bin/webpack (Errno::ENOENT) Question Question
How did my database got hacked ? Question Question

Question

What is the proper way to sync assets with Digital Ocean Space when precompiling assets?

Posted April 18, 2019 2.9k views
Ruby on RailsDokkuUbuntu 18.04

I deployed RoR application using Dokku On Digital Ocean droplet. I’m going to try DO Space CDN.
I’d like assets to be synchronised to S3 bucket after run bundle exec rake assets:precompile but I can’t find any info about how should precompiled assets be copied to DO space.
I read about ‘asset_sync’ gem but i’m not sure about it. Does anyone have some thoughts?

Add a comment
slavadc5f09a0f97c6e8e69b16
By:
slavadc5f09a0f97c6e8e69b16

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Deployment fails for Rails App with App Platform - No such file or directory - /workspace/node_modules/.bin/webpack (Errno::ENOENT) Question Question
How did my database got hacked ? Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer
moisey October 8, 2019

Because the Spaces API is compatible with AWS S3’s API you should be able to use most of the same gems and tooling that’s pre built for AWS.

For example fog-aws works with DigitalOcean spaces
https://github.com/fog/fog-aws

With that in mind you should be able to use asset_sync with Spaces.

Use your DigitalOcean Spaces Key instead of the AWS Key and use ${REGION}.digitaloceanspaces.com as your endpoint instead of the AWS S3 region endpoint.

Reply Report

Related

Looking for something else?

Ask a new question Search for more help