952024 - Host the working version of mciconf on mozqa.com

Status: RESOLVED FIXED

(Mozilla QA Graveyard :: Infrastructure, defect)

Description

[Cosmin Malutan, [:cosmin-malutan]]

Due to fact that the code and staging version would live on github.com/mozilla/mciconf, asdiscused on bug 951578, we would want the live version on mozqa.com

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Brandon, what is the best way to get the code updated on mozqa.com? I assume via a cron job similar to the other external repositories, and an update for puppet?

The code we want to have synced is:
https://github.com/mozilla/mciconf/tree/release

Comment 2

[Brandon Burton [:solarce]]

(In reply to Henrik Skupin (:whimboo) from comment #1)
> Brandon, what is the best way to get the code updated on mozqa.com? I assume
> via a cron job similar to the other external repositories, and an update for
> puppet?
> 
> The code we want to have synced is:
> https://github.com/mozilla/mciconf/tree/release

From a quick glance, it looks like this application is static content on the filesystem? is that correct?

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+2]]

That's correct. There are no scripts running server-side. All is done via JS in the browser.

Something I missed to say is that the target location should be http://www.mozqa.com/mciconf.

Comment 4

[Brandon Burton [:solarce]]

When just pulling down a git checkout, the URL ends up being http://www.mozqa.com/mciconf/app/ , is that fine or should I do some symlink trickery to make it just http://www.mozqa.com/mciconf/ ?

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Cosmin, I assume the app sub folder is not necessary and we can move all the files into the top level folder in the repository. Is that right? If yes, can you please do that?

Comment 6

[Cosmin Malutan, [:cosmin-malutan]]

I moved it.
https://github.com/mozilla/mciconf/pull/7

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+2]]

(In reply to Brandon Burton [:solarce] from comment #4)
> When just pulling down a git checkout, the URL ends up being
> http://www.mozqa.com/mciconf/app/ , is that fine or should I do some symlink
> trickery to make it just http://www.mozqa.com/mciconf/ ?

No, that's fine then. It will work once we push the next version to the release branch. So it looks great. Thanks Brandon!

Comment 8

[Dave Hunt [:davehunt] [he/him] ⌚BST]

We'll also need to update https://mana.mozilla.org/wiki/display/websites/mozqa.com

Comment 9

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Cosmin, after nearly two weeks  I would like to see an update from you here.

Comment 10

[Cosmin Malutan, [:cosmin-malutan]]

Hi, sorry if I missed this, I opened a new pr for this https://github.com/mozilla/mciconf/pull/8. The thing is if I get only this landed then I would have to do a lot of work for the requireJS commit, and I would like to have that landed too since is more profesional to split the application into relevant smaller files instead of a single javascript file.

Again the pr for this is:
 https://github.com/mozilla/mciconf/pull/8
If you want to land both the requireJS and removal of app directory commits:
 https://github.com/mozilla/mciconf/pull/7

Thanks

Comment 11

[Henrik Skupin [:whimboo][⌚️UTC+2]]

We want to have PR #7 without the change for this bug! I already mentioned that over on PR #7 more than a week ago. Please really follow your github email, so that things are not getting massively delayed.

Comment 12

[Cosmin Malutan, [:cosmin-malutan]]

Henrik, in pr 8, I only removed the app directory.
I will update the pr 7 later(requireJS commit).

Comment 13

[Henrik Skupin [:whimboo][⌚️UTC+2]]

All what we can do here has been done. The mciconf application is now fully functional on mozqa.com.