Serve up the Bespin client from a web server

VERIFIED FIXED in 0.1

Status

P1
blocker
VERIFIED FIXED
10 years ago
10 years ago

People

(Reporter: dion, Unassigned)

Tracking

Details

(Reporter)

Description

10 years ago
Currently, the client piece is loaded in locally for development. Create a deployment where it is hosted, and then we can add logic on the server (enforce login, proxy for resources).
(Reporter)

Updated

10 years ago
Severity: normal → blocker
Priority: -- → P1
Whiteboard: infrastructure

Comment 1

10 years ago
The new Python server serves up the static files as well for development environments, so I believe this bug is complete. I will open a separate bug for the "proxy for resources" part, which is basically the ability to enter a URL for a new Bespin command to install.

Comment 2

10 years ago
The main issue of this is done. bug 473296 covers plugin installation.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Group: mozilla-corporation-confidential
This is a mass migration from Mozilla Labs :: Bespin to Bespin :: Infrastructure.
Component: Bespin → Infrastructure
Product: Mozilla Labs → Bespin
Whiteboard: infrastructure
Target Milestone: 0.1 → 0.1.x
QA Contact: bespin → infrastructure
Present in the original commit, changeset fb786086bc9e. Marking as VERIFIED.
Status: RESOLVED → VERIFIED
OS: Mac OS X → All
Hardware: x86 → All
Target Milestone: 0.1.x → 0.1
You need to log in before you can comment on or make changes to this bug.