Closed Bug 425995 Opened 16 years ago Closed 16 years ago

Weave should support non-mangled user id's for dedicated hostings

Categories

(Cloud Services :: General, enhancement, P1)

Product:
Cloud Services
Component:
General
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: iav, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008032904 Minefield/3.0pre
Build Identifier: 

Now weave stores user data in folder, produced with some caching from user id.
It is not suitable for small servers.
Need possibility to use user id as part of the storage path, and to set full path to user profile on server.

First case:
data stores on server like 
/weave/user1/xxx
/weave/user2/xxx

second case (user enters full path):
/~user1/weave/
/user2/weave
/robot-a/central/


Reproducible: Always
Targeting for 0.2.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Priority: -- → P1
Hardware: PC → All
Target Milestone: 0.1 → 0.2
Blocks: 433979
Status: NEW → ASSIGNED
service-side components updated, waiting for SSL configuration before propagating changes
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Component: Weave → General
Product: Mozilla Labs → Weave
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.