We plan to release a public beta of FlightDeck by the end of Q2, at which point FlightDeck is likely to get a lot of attention. Therefore, we should make sure that the database it uses can be scaled up as demand increases. Currently, we're using SQLite, which, despite being the little database engine that could (and one that is near and dear to my heart), is not scalable to the extent it would need to be for a service being provided to a potentially quite large Mozilla community of addon developers. Thus, we should replace it with something more scalable. In theory, we can use anything supported by Django. Piotr has previously used MySQL with Django, however, and we're pretty familiar with MySQL here at Mozilla, so it seems like a good choice. In order for the staging server to be a true staging server, it should use the same database as the preview server, so we can stage changes to the application against the exact same data as the preview server uses. However, it should also be possible to temporarily make a copy of the database and run the staging server against that copy, for those situations in which we need to stage an application update that makes breaking changes to the database.
(In reply to comment #0) > In order for the staging server to be a true staging server, it should use the > same database as the preview server, so we can stage changes to the > application against the exact same data as the preview server uses. By "preview" I assume you're talking about the AMO preview site?
(In reply to comment #1) > By "preview" I assume you're talking about the AMO preview site? I'm actually talking about the FlightDeck preview site: https://lm-app-flightdeck01.mozillalabs.com/ In this case, the word "preview" refers to a pre-production version of a site that is being made available for use in order to provide its features to its audience while they are under development and gather feedback on how to improve that functionality. It is the server we are going to use for the public beta release of the site that we plan to do by the end of the quarter.
The SQL database is up and running, and stage is fully updated and running from MySQL. Dev is also running, but using sqllite. Marking fixed, as cutting the public preview over to new code is a separate bug.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.