On 6/17/14 11:07, Dan Callahan wrote:
On Thursday, I'll take the responses I've received and turn that into a
formal proposal.
Alright, upon reviewing the replies, some of which didn't make it
through to the lists, I'm pretty confident that:
- Folks want support on a wide variety of platforms.
- Mozilla employees are likely to use AWS (with fxa-dev) or their local
machine (with npm / pip install).
- Self-hosters are unlikely to use fxa-dev, as "it creates too many
moving parts," and it currently contains "non-essential Mozilla specific
bits."
- We're not the right people to build RPMs or Debs; we should focus on
source and instructions instead.
- Many self-hosters want to use OwnCloud, which means our own code
doesn't necessarily have to be the preferred path for self-hosting, just
a reasonable one.
With that in mind, I'd like to move forward with the following specific
targets:
1. Add Sync to Danny's fxa-dev.
This ensures that self-hosted Sync is a part of Mozilla's normal QA
/ Dev environment.
2. "Minimal" Vagrant + Ansible scripts for Ubuntu 14.04 LTS, and
possibly CentOS 7.
The primary goal of the script is not to be executed by
self-hosters, but rather to act as executable (testable, verifiable)
documentation for self-hosting. Thus, legibility is my primary concern.
Ansible Playbooks and Dockerfiles seem to be the best options, and I'm
leaning toward Ansible as it's currently being used by Danny's fxa-dev
project.
3. Generally improved documentation.
Since it sounds like most self-hosters will be rolling their own setup.
Additionally, I'd love to work with someone in the community to:
4. Get self-hosted Sync working on a PaaS like Heroku.
Mainly a proof of concept, but what a cool blog post that would make!
If anyone objects (or concurs!), let me know,
-Callahad
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
