I've gone to the effort of building RPMs for Mozilla Sync Server &
required dependencies for RHEL 5 & 6 platforms & of course clones such
as CentOS.
http://www.jethrocarr.com/2012/03/04/mozilla-sync-server-rpms/
They aren't perfect, but hopefully will be useful to anyone wanting to
get up and running with sync server quickly and easily on a RPM-based
platform. :-)
regards,
jethro
--
Jethro Carr
www.jethrocarr.com
www.amberdms.com
hi all, I've gone to the effort of building RPMs for Mozilla Sync Server & required dependencies for RHEL 5 & 6 platforms & of course clones such as CentOS. http://www.jethrocarr.com/2012/03/04/mozilla-sync-server-rpms/ They aren't perfect, but hopefully will be useful to anyone wanting to get up and running with sync server quickly and easily on a RPM-based platform. :-) regards, jethro
_______________________________________________ Services-dev mailing list Servic...@mozilla.org https://mail.mozilla.org/listinfo/services-dev
That's awesome, will review and see what improvements I can make to it
based on an outsider's experience this weekend.
Having said that, you guys have done a pretty good job at improving
stuff since I first started looking at in back in December, such as
fixing up the sample configurations. :-)
> In the long run, we'd like to move the user-level guides to
> https://developer.mozilla.org/ (a wiki) so anybody can more easily
> edit them. I don't believe anybody is actively working on that now or
> plans to. Any contribution you or anyone else could make would be very
> much appreciated.
Would be happy to help. :-)
Maybe first step is to get some contributions into the current doc
system and then look at next step turning it into the wiki?
> To answer your question in your post's comments about client backwards
> compatibility with Sync Protocol 2.0, we are still flushing that out.
> There should be an email to this list with regards to that shortly.
Cool stuff. :-)
Anything you can do would help. The lowest hanging fruit is to probably
fork the docs repo on GitHub and edit ReST right in your browser.
Although, somewhere along the way the changes will need to be tested
with Sphinx. If you can do that testing to save the inevitable
back-and-forth on accidentally pushing busted changes, that would be
awesome.
Moving things from ReST to MDN (developer.mozilla.org) is a mind-numbing
task. I won't ask you to do it. But, I won't stop you either ;)
> Moving things from ReST to MDN (developer.mozilla.org) is a mind-numbing
> task. I won't ask you to do it. But, I won't stop you either ;)
hmmm it might be easier to just start porting and correcting at the same
time - do you have a documentation structure in mind for Mozilla Sync on
MDN at this stage?
Don't worry, I love mind-numbing tasks, remember I package things into
RPMs for fun. ;-)
Current MDN content lives at
https://developer.mozilla.org/en/Firefox_Sync. I think something like
/Firefox_Sync/Server or /Firefox_Sync/Server_Guide would be an
appropriate place to start dropping content. Or, perhaps create
/Sync_Server. Naming is hard. We can always move pages around later (I
think).
Sounds good - I'll start some up this weekend, port some content across
and make some changes and post back to this list to get thoughts about
whether it's the right sort of thing.
I'm sure people like Fabian will be able to add some excellent content
about non-Linux UNIX platforms to it and the wiki makes barrier to entry
pretty low. :-)
hi all, I've gone to the effort of building RPMs for Mozilla Sync Server & required dependencies for RHEL 5 & 6 platforms & of course clones such as CentOS. http://www.jethrocarr.com/2012/03/04/mozilla-sync-server-rpms/
They aren't perfect, but hopefully will be useful to anyone wanting to get up and running with sync server quickly and easily on a RPM-based platform. :-) regards, jethro
On 06.03.2012 02:28, Jethro Carr wrote:
> I'm sure people like Fabian will be able to add some excellent content
> about non-Linux UNIX platforms to it and the wiki makes barrier to entry
> pretty low. :-)
Sure, I can do this. But also feel free to use the ideas from my
guide when starting the wiki page. I guess you will need some
thinking about the whole structure of the page with the different
chapters to use.
bye
Fabian