Hi all, (cross posted to fxa-dev and sync-dev)
I'm trying to figure out how we can make it easier for folks to run
their own FxA + Sync stacks, and I'd need your input. Specific questions
are at the end of this post. If you're on this list, you're part of the
target audience. Please respond to them. By Wednesday night.
I have three goals:
1. An enthusiast with moderate *nix skills should be able to get our
server-side code up and running in about 15 minutes on a supported platform.
2. Whatever tooling we use should be grokkable to someone without
experience in that particular tool. Specifically, they should be able to
can manually deploy services on other, unsupported platforms by reading
through the configuration scripts.
3. Our solution should be useful for core engineers and QA when doing
their own local development or testing.
The trick is, I don't think there's an obvious "best" solution for
achieving those goals.
Right now, Danny Coates maintains the dannycoates/fxa-dev repo, which
powers the FxA dev environment. It uses Packer to provision AWS or
Virtualbox machines, and Ansible for configuration. However, it's not a
perfect fit for self-hosting: it targets Scientific Linux, rather than
the more common enthusiast distros (Ubuntu, Mint, Arch), and it's
relatively heavyweight. Self-hosters probably don't need Heka, Elastic
Search, and Kibana, for instance.
Before we roll forward with fxa-dev as a fait accompli, I'd like to step
back and ask a few questions:
0. Are those the right goals? Am I unnecessarily conflating anything?
1. What platforms should we support?
2. Are there any configuration management systems that you've had a
particularly good or bad experience with? Any suggestions for what we
should use?
3. Would you, yourself, use the above system for local development or
testing? Why / why not?
4. How should we package and distribute the services?
5. Are you currently using the fxa-dev repo locally? Why / why not? What
has your experience been?
On Thursday, I'll take the responses I've received and turn that into a
formal proposal.
Thanks for helping make this awesome,
-Callahad
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
