427707 - Fix up stage server for party tool 2.0

Status: RESOLVED FIXED

(Webtools Graveyard :: Party Tool, defect, P1)

Description

[Michael Morgan [:morgamic]]

Need to set up a stage server running the new code hosted on MoCo servers, probably behind LDAP.

https://firefoxparty.stage.mozilla.com/ is pretty hosed, so we'll have to fix that and make sure it's pulling from the most recent trunk.

A part of this might be getting the code into SVN so it's easier to tag/deploy.

Comment 1

[Alex Polvi]

It's in SVN. Last I heard we were waiting on schema updates.

Comment 2

[Michael Morgan [:morgamic]]

Ryan - can we get the updated schema so we can stage the current code?

Comment 3

[Ryan Flint [:rflint] (ping via IRC for reviews)]

I'll have the new schema landed tonight along with a batch of other fixes for your staging pleasure. :)

Comment 4

[Alex Polvi]

Over to IT for staging. 

Code lives at: http://svn.mozilla.org/projects/mozparty/
Old site lives at (find to reuse): https://firefoxparty.stage.mozilla.com/

I think there were a bunch of schema changes, so just starting with a fresh db is fine. 

Comment 5

[Alex Polvi]

Also, we'll need HTTP auth (moz ldap if possible). Woot.

Comment 6

[Justin Fitzhugh]

Can we get a production acceptance section for this before it's staged?

Comment 7

[Alex Polvi]

Never done one of those before, could you point me in the right direction?

It's currently in prod here: http://firefoxparty.com/

Comment 8

[Alex Polvi]

whoops, didn't mean to re-assign.

Comment 9

[Alex Polvi]

sorry for the bug spam

Comment 10

[Reed Loden [:reed]]

(In reply to comment #7)
> Never done one of those before, could you point me in the right direction?

http://wiki.mozilla.org/IT/Production_Acceptance

Comment 11

[Alex Polvi]

thanks Reed.

How is this for a first swing? 

http://wiki.mozilla.org/IT/Production_Acceptance/mozilla-party

Comment 12

[Jeremy Orem [:oremj]]

I'm getting:

2008-04-29 14:58:47 Warning: Warning (512): Cache not configured properly. Please check Cache::config(); in APP/config/core.php in [CORE/cake/libs/configure.php, line 621]

App is staged at https://firefoxparty.authstage.mozilla.com/

Comment 13

[Alex Polvi]

Thanks oremj, over to buchanae to start work'n out the kinks. 

buchanae, the svn repo can be found at: http://svn.mozilla.org/projects/mozparty/

Probably want to setup your own stage, but oremj has setup stage to pull svn periodically.

Main issues now are:

* Cake caching errors
* Google API key(s)
* Debugging statements

Other bugs - to be figured out later (probably in a new bug)
* Register page seems hosed: https://firefoxparty.authstage.mozilla.com/users/register
* Create a party hosed: https://firefoxparty.authstage.mozilla.com/events/add/

Comment 14

[Ryan Flint [:rflint] (ping via IRC for reviews)]

(In reply to comment #12)
> 2008-04-29 14:58:47 Warning: Warning (512): Cache not configured properly.
> Please check Cache::config(); in APP/config/core.php in
> [CORE/cake/libs/configure.php, line 621]
Should be taken care of with r12661 - I forgot that SVN doesn't track empty directories. app/tmp/cache/* will also need to be writable if it isn't already.

(In reply to comment #13)
> Main issues now are:
> 
> * Cake caching errors
> * Google API key(s)
> * Debugging statements
Already on these.

> Other bugs - to be figured out later (probably in a new bug)
> * Register page seems hosed:
> https://firefoxparty.authstage.mozilla.com/users/register
> * Create a party hosed: https://firefoxparty.authstage.mozilla.com/events/add/
Oremj: what version of PHP is this running with?

Comment 15

[Jeremy Orem [:oremj]]

PHP 5.1.6

Comment 16

[Alex Polvi]

(In reply to comment #14)
> > Other bugs - to be figured out later (probably in a new bug)
> > * Register page seems hosed:
> > https://firefoxparty.authstage.mozilla.com/users/register
> > * Create a party hosed: https://firefoxparty.authstage.mozilla.com/events/add/
> Oremj: what version of PHP is this running with?

Create a party is at least looking better. Registration is still hosed. Ryan, are you done with your changes so we can have webdev take over?

Comment 17

[Alex Polvi]

now broken on OID errors... any ideas?

Comment 18

[Ryan Flint [:rflint] (ping via IRC for reviews)]

(In reply to comment #17)
> now broken on OID errors... any ideas?
> 

It's waiting on me to file a request to have the database re-imported and there's no point in doing so until 431794 is fixed.