Closed Bug 1027487 Opened 6 years ago Closed 6 years ago
Point FMD Client to New STG Server URL
Here's the URL: https://fmd.stage.mozaws.net
I'm also unclear if this is truly a staging server or a stable end point on the dev server but I'm not going to over-rotate on semantics. We just need the client to talk to correct URL. Thank you.
We also need to use staging oauth: https://oauth.stage.mozaws.net/v1 highly recommend making this use a pref that can be set in prefs.js such as: user_pref("toolkit.fmd.app.uri", 'https://fmd.stage.mozaws.net'); user_pref("toolkit.fmd.oauth.uri", 'https://oauth.stage.mozaws.net/v1');
Our current setup is to store these URLs in Gaia, not Gecko, so tweaking them only requires changing gaia://customization/findmydevice.json , which seems to be just as easy as using prefs.js. Would that suffice for testing? 1- https://github.com/mozilla-b2g/gaia/blob/master/customization/findmydevice.json
(In reply to Erin Lancaster [:elan] from comment #1) > I'm also unclear if this is truly a staging server or a stable end point on > the dev server but I'm not going to over-rotate on semantics. The role of fmd.stage.mozaws.net is to provide a consistent platform for testing and external integration. It pulls from https://github.com/mozilla-services/FindMyDevice:master. If there is a change, I will pull and restart before 0900 Pacific the following day. Efforts will be made to ensure that the platform is operational. The role of fmd.dev.mozaws.net is for localized development and component integrations (e.g. web ui builds, FxA integration, server db tweaking, etc.). It will change more often as bugs are encountered or addressed.
in response to comment #3 - yes editing that file works for me.
6 years ago
Assignee: ggoncalves → 6a68
Comment on attachment 8442981 [details] [review] Github PR 20762 Thanks! Talking to :jrconlin on IRC, he would also like to bump the version to 1. Can you please do that too?
Attachment #8442981 - Flags: review?(ggoncalves) → review+
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
NI Jared to help land this on 2.0 as ryan is out until Monday and QA needs this fixed. How do I uplift to 2.0? Checkout the gaia v2.0 branch , commit your patch and push. Gaia checkins should automatically get pushed to aurora via the bumper bot within 20 minutes of landing to git after which make sure you have a green tree : https://tbpl.mozilla.org/?tree=Mozilla-Aurora
Hi Bhavana - Sadly, I don't know how the uplift process works. I'll see if someone in #gaia can offer help.
Aha, you were right: [14:58:39] <fabrice1> _6a68: do a PR against 2.0 [14:58:43] <fabrice1> and merge it Would you like me to do this in github?
RyanVM is taking the day off, and nobody is sheriffing (!), so I uplifted this manually. v2.0: https://github.com/mozilla-b2g/gaia/commit/766c3d71c018b8f055371f649daa16fbd5d5a460
:ggp is there a way to update gaia://customization/findmydevice.json on device. I can't find such a file in gaia on device. Having to edit and flash image isn't ideal when we're testing a build from the build machines.
(In reply to Edwin Wong [:edwong] from comment #15) > :ggp is there a way to update gaia://customization/findmydevice.json on > device. I can't find such a file in gaia on device. Having to edit and > flash image isn't ideal when we're testing a build from the build machines. Hmm, not that I know of, but it might be worth checking with someone who works on the Gaia build system. Since FMD currently doesn't have any Gecko bits either, switching to prefs now might also be difficult. But we can try to work something out next week, if that's ok with you.
Hey Edwin, I looked through the code a bit, and the output file corresponding to customization/findmydevice.json is build_stage/settings/resources/findmydevice.json. Does this help at all with finding that file on device? If not, I can help look through the Makefile a bit more on Monday (to figure out how build_stage corresponds to on-device codepaths.  https://github.com/mozilla-b2g/gaia/blob/master/apps/settings/build/build.js#L31-L43
You need to log in before you can comment on or make changes to this bug.