Skip to content
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.

Please add the ability to point to custom syncserver. #1129

Closed
tublitzed opened this issue Jan 7, 2020 · 4 comments
Closed

Please add the ability to point to custom syncserver. #1129

tublitzed opened this issue Jan 7, 2020 · 4 comments
Labels
effort-XL Expected to take more than a sprint (or unknown) for engineering to complete. enhancement Issue describes an improvement or addition to the product. feature feature-sync needs-design
Projects
Lockwise Mobile

Comments

@tublitzed
Copy link

tublitzed commented Jan 7, 2020 •
edited
Loading

Why/User Benefit/User Problem

It'd be ideal not to have to do a custom Lockwise build to test Sync changes against staging. If there were a flag/config pref/toggle somewhere that would let us either:

a) Point to staging only
OR
b) Set our own sync host (which would allow pointing to staging and might be more flexible for self-hosters?).

then we could make changes to Sync with more confidence that we can test them against staging before rolling to prod.

Acceptance Criteria (how do I know when I’m done?)

  • We're able to point Lockwise to staging based Sync server in Fenix.

Not included

  • Fennec - I don't think it's needed right now since Fenix is close; probably not worth the effort.
@tublitzed tublitzed mentioned this issue Jan 7, 2020
Open
4 tasks
@eliserichards eliserichards added this to Inbox in Lockwise Mobile via automation Jan 7, 2020
@eliserichards eliserichards added enhancement Issue describes an improvement or addition to the product. feature-sync labels Jan 7, 2020
@eliserichards
Copy link
Contributor

Related to #542

@ddurst
Copy link
Contributor

ddurst commented Jan 7, 2020

Related to mozilla-lockwise/lockwise-ios#1175

@ddurst ddurst mentioned this issue Jan 7, 2020
Open
@eliserichards eliserichards added needs-design effort-XL Expected to take more than a sprint (or unknown) for engineering to complete. labels Jan 7, 2020
@eoger
Copy link

eoger commented Mar 11, 2020

Is this the same as #542? Should we close one of the two? Just so you know I'm working on this on the a-s side.

@eoger eoger mentioned this issue Mar 11, 2020
Closed
@tublitzed
Copy link
Author

@eoger ah, yup. I'll close this out as a dupe and we can track via #542

Lockwise Mobile automation moved this from Inbox to Done Mar 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
effort-XL Expected to take more than a sprint (or unknown) for engineering to complete. enhancement Issue describes an improvement or addition to the product. feature feature-sync needs-design
Projects
Lockwise Mobile
  
Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ddurst @tublitzed @eoger @eliserichards