Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Neos: Assets in the Cloud - Inspiring Conference 2015

More than two years in the making, the new cloud-capable asset management finally is available in Flow 3.0 and Neos 1.3. With its companion, the new Media package, it provides a sophisticated but easy-to-use API for developers to manage media assets. In this session you'll learn how to create and manipulate images, use local and remote storages, publish to Content Delivery Networks and even create your very own storage and publishing solutions.

  • Loggen Sie sich ein, um Kommentare anzuzeigen.

Neos: Assets in the Cloud - Inspiring Conference 2015

  1. 1. Assets in the Cloud by Robert Lemke
  2. 2. What the Asset?
  3. 3. Webserver Database Shared Filesystem
  4. 4. Webserver Database Cloud Storage
  5. 5. Webserver Database Cloud Storage
  6. 6. Webserver Database Cloud Storage
  7. 7. Webserver Database Cloud Storage Dropbox / GDrive CDN
  8. 8. O N
  9. 9. Building Blocks
  10. 10. Resource A resource is the atom of assets; it is the representation of data which is usually stored as a file. It is best practice to not share Resource objects between multiple parents.
  11. 11. Resource Pointer There are NO Resource Pointer objects anymore in Flow 3.0.
  12. 12. Static vs Persistent Static resources are deployed as part of the code base. They never change during runtime. Persistent resources is data uploaded, created or imported by the application. Each resource is registered in the database.
  13. 13. Storage Resources are stored in internal storages which are only accessible to your application. There are writeable and read-only storages.
  14. 14. Publishing Target Resources are published to Publishing Targets. The Publishing Target provides a public URL to a single or multiple resources.
  15. 15. Collection Each resource belongs to one collection. A collection defines the storage and publishing target to use for the contained resources.
  16. 16. Common Tasks
  17. 17. Publish to a CDN
  18. 18. Import a PDF file
  19. 19. Upload an image
  20. 20. Get a URL for a resource
  21. 21. Media
  22. 22. Asset Image Audio Document Video Image Variant Crop Adjustment B/W Adjustment Thumbnail
  23. 23. What else?
  24. 24. S3 / WebDAV / GDrive …
  25. 25. CSS path rewriting
  26. 26. Filters
  27. 27. robert@flownative.com www.flownative.com @robertlemke share your thoughts