• VM-Content
  • Setup
    • Minimal
    • Optimal
  • Services
  • Specification

VM-Content¶

Setup¶

Minimal¶

• 1 VM-Content in M-Web
• Identification of the content server with HOSTNAME
• Mount per samba in VM-Web and VM-Processing in ./content/
• Serving of a file via URL on VM-Web

Optimal¶

• 1 VM-Content in each M-Content
• Identification of the content server with URL and HOSTNAME
• Mount per samba in VM-Processing in ./content/
• Stand-alone pyramid webservice
• Distribution of new previews to all instances of VM-Content via script
• Serving of a file via URL on VM-Content
• Dynamic connection of an instance of VM-Content to the client
  • VM-Nginx load balances the content url to one instance of VM-Content
• Authentification
  • Service: Service-Token (per Service, i.e. per VM-Content)
  • User: Cookie-ID (background request forwarded to VM-Web API)

Services¶

• Sambaserver
• (optimal) Webservice: Authentification, Content server
• (optimal) Script: Content Distribution

Specification¶

• Content storage for static files of CONTENTTYPE (previews, excerpts)
• (optimal) Content provider for user clients
• For further details, see Specification