[DTPT] Update Dev and Stage for De Todos Para Todos (to support database)

RESOLVED FIXED

Status

Infrastructure & Operations
WebOps: Other
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: ckoehler, Assigned: jd)

Tracking

Details

(Reporter)

Description

6 years ago
The updated code for DTPT now requires a database. Connection details are in bug 725696.

Please update the dev and stage environments with the most recent changes from Github and setup database support as follows:

1.. Update db name and credentials in tab/db.config.php (copied from db.config.php.sample).
2. Run tab/mysql/feb012012.sql from command line.
3. Block web access to tab/mysql/feb012012.sql via apache conf (or less us know if it should be done via htaccess).

Thanks!
Can you please explain the reasoning behind wanting access to the .sql file done, when it's available on https://github.com/Nobox/Mozilla-DeTodosParaTodos-Site/blob/master/tab/mysql/feb012012.sql for anyone to get?
Not done, but blocked
Assignee: server-ops → bburton
Status: NEW → ASSIGNED
Assignee: bburton → jcrowe
(Reporter)

Comment 3

6 years ago
(In reply to Brandon Burton [:solarce] from comment #1)
> Can you please explain the reasoning behind wanting access to the .sql file
> done, when it's available on
> https://github.com/Nobox/Mozilla-DeTodosParaTodos-Site/blob/master/tab/mysql/
> feb012012.sql for anyone to get?

That's a good point. Please disregard that step.
(Reporter)

Comment 4

6 years ago
(In reply to Brandon Burton [:solarce] from comment #2)
> Not done, but blocked

What is blocking this?
Sorry, poor choice of words. I wrote "Can you please explain the reasoning behind wanting access to the .sql file *done*" and meant "Can you please explain the reasoning behind wanting access to the .sql file *blocked*.

:jd is working on this now :)
(Assignee)

Comment 6

6 years ago
Christie,

Sorry for the delay.  Due to some confusion the databases were created on the incorrect servers.  This has been corrected.  I created databases for dev/stage/prod and imported feb012012.sql for all three.

I created the tab/db.config.php file for all three instances as well.  I updated both dev and stage from github.  The change is already set up on prod so it will get this configuration on the next push/update.

As per the previous discussion I did not block access to the feb012012.sql file through Apache.

Please let me know if you need further assistance or if anything does not work as expected.

Regards
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Reporter)

Comment 7

6 years ago
Thanks, JD. I'm getting an error at this page (the one that uses the db), will you take a look?
http://detodosparatodos-dev.allizom.org/tab/
(Assignee)

Comment 8

6 years ago
Fixed it, that was my fault.  Should be good to go now.

Cheers
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.