Closed
Bug 971998
Opened 11 years ago
Closed 11 years ago
Evaluate static content delivery platform (hosting platform for web files)
Categories
(Hello (Loop) :: Server, defect)
Hello (Loop)
Server
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: abr, Unassigned)
References
Details
User Story
For non-Firefox desktop uses of Loop, we need to store the pages for other applications on a server somewhere. These may also need localisation of some form - see bug 972884 - the result of that may impact if we need templating or not.
No description provided.
Comment 1•11 years ago
|
||
We need to evaluate some potential static content delivery platforms. Need to define a list first.
Component: General → Server
Comment 2•11 years ago
|
||
About CDNs, https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=1081607&src=search is a good resource here.
Updated•11 years ago
|
Summary: Evaluate static content delivery platform → Evaluate static content delivery platform (hosting platform for web files)
Comment 3•11 years ago
|
||
For development we want to use the express.js serving utility of loop-client: https://github.com/mozilla/loop-client and having the GET /calls/:token to do a 302 to it (using the configuration)
The configuration could be: {appUrl: "http://localhost:6000/#{token}"}
Assignee: nobody → rhubscher
Comment 4•11 years ago
|
||
I will leave this bug for production CDN choice and alexis created the bug 984946 for the development environment part.
Assignee: rhubscher → nobody
Comment 5•11 years ago
|
||
Closing for now, this is a call for ops to make on deployment.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•