F.A.Q
Un-rendered components delegate the rendering to the clients. This is useful for performance and cacheability. More details about rendered components and about un-rendered components
Yes! Either you use Cloudfront or any other vendor's on top of the S3, you will get a url, for instance https://123456789.cloudfront.org/... or https://my-cdn.my-company.com. Then set the s3.path property in the registry configuration.
There is no support for other vendors at the moment. But if you feel like you would get some value on integrating other vendors or investigating other approaches, let us know, we would be happy to discuss that, especially if you would be able to contribute with some Pull Requests. Just open an issue first and join the conversation!
I already use S3 to save my assets via a consolidated build pipeline. Can I reference this files from my OC components?
Yes. OC allows you to bundle all the resources a component needs inside itself (and takes care of putting all the stuff in place during the publishing), but you are free to link (absolutely) any other static asset inside your components' markup. OC will still need S3 for saving its stuff though: if you decide to share the same S3 bucket (probably because you already got a configured CDN on top of it) be careful! In particular,
- OC heavily relies on S3 for its operations. Dedicating its own bucket is a good measure for limiting it to interfere with any other application.
- OC saves some files with different ACL policies when a component is published. If your bucket is already configured to be completely public (it may be the case if you use it for hosting a static site), this may not be good for OC as you may not want to expose some private stuff. In this case, you may need to get a separate bucket so that you can apply the appropriate configuration.
