Firefox OS/Performance/Automating Datazilla Developer Setup: Difference between revisions
< Firefox OS | Performance
Jump to navigation
Jump to search
m (Lakrits moved page FirefoxOS/Performance/Automating Datazilla Developer Setup to Firefox OS/Performance/Automating Datazilla Developer Setup: The official spelling of "Firefox OS" leaves a space between the two parts of the name. It's easier to...) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 14: | Line 14: | ||
==Bugs== | ==Bugs== | ||
No meta bug created yet. | No meta bug created yet. | ||
==Contacts== | |||
* [https://mozillians.org/en-US/u/dhuseby/ Dave Huseby] | |||
* jeads on irc.mozilla.org | |||
Latest revision as of 13:59, 1 February 2015
Introduction
Currently, getting a local instance of Datazilla set up for development is non-trivial. Vagrant and Docker could be used to automate the provisioning of a local Docker instance that is set up correctly for Datazilla hacking.
Project Plan
We have already gone through the process of setting up Vagrant to provision a development environment for our TreeHerder web app. The documentation on how to install TreeHerder using Vagrant is here. The TreeHerder Vagrant file is here.
To be successful in this project, the following has to be accomplished:
- Build a base Vagrant file to provision a Docker instance running Ubuntu 13.04. This will be used as the base for a number of other similar projects.
- Build upon the base Vangrant file to provision the Docker instance with the necessary prerequisites for running Datazilla.
- Add automation to the provisioning process to clone the Datazilla code and to set up a local database with test data.
- Write an MDN article documenting how to use Vagrant to provision a Datazilla development environment.
Bugs
No meta bug created yet.
Contacts
- Dave Huseby
- jeads on irc.mozilla.org