Updates - Hotfixes without a Connect account?

Here's a question from a Nuxeo Newbie's perspective because I'm still not getting it.

I work for a small non-profit and there's not any way for us to afford the $47,000 per year for a Connect account. Our needs are simple and I'm willing to do the hard work of keeping things updated manually. What I can't seem to figure out is the exact process for installing hot-fixes without a paid Connect account. (Side note: I don't expect everything for free and I want Nuxeo to be successful so that they stay around. I just need some clear documentation to be able to do what they claim is possible.)

As I've searched for answers, I'm confused by the info I've read in the following post: http://answers.nuxeo.com/questions/8093/is-it-not-possible-to-run-all-updates-without-a-nuxeo-connect-account

I read Florent's response: “Nuxeo LTS (Long Term Support) hotfixes via Nuxeo Connect is a service we provide that gives registered users very simple updates to the latest hotfix version of Nuxeo. That takes time and resources on our part. We don't think that registering through Nuxeo Connect to get this service is that much of a hurdle (it's free)”

I can't figure out how to register through Nuxeo Connect. I see lots of ways to sign up for a 30 day trial, but not a way to just register. Maybe things have changed since February of 2014.

Maybe it's as Julien stated: “Applying updates manually means either stick to the FastTrack version (which is equivalent to the latest LTS + hotfixes + new features), or reading the wanted resolved JIRA issues, build and deploy the source code including the fix, or building a whole distribution from the source code.”

If so, that's fine. Can someone point me to any DETAILED instructions on how to do this?

I'd just like to figure out the correct way to go about this and it doesn't seem like Julien and Florent are saying the same thing. i'm sorry that I couldn't figure this out after days of searching through the documentation. But it seems that all the documentation is written assuming you've got a Connect account.

I love the possibilities that I see with Nuxeo, but at this rate, I'm not sure we can make it work.
Thanks to anyone who can help me understand this!

2 votes

1 answers



If you discover a reproducible set of steps to do this, I'd also love to know. Happy to give you a hand documenting, even.

bhotrock, did you get any further with this one by any chance?

I'm sorry I didn't respond months ago. I had hoped to have time to work on this, but finally decided that it was just to time consuming to work through. I don't think our organization is Nuxeo's target. So I've started looking elsewhere. There are some other projects that I hope will be able to meet our needs. Looking at OwnCloud and Pydio. (Not sure if mentioning these is allowed, but I don't think they are competitors. The target audience seems to be much different.)

I'm lucky enough to be working somewhere with the Studio subscription, but if I needed to do this, I would start with the developer documentation at https://github.com/nuxeo/nuxeo/blob/master/README.md.

Under “Deploying,” where they write

git clone git@github.com:nuxeo/nuxeo.git
cd nuxeo
python clone.py master -a

I would use the hotfix tag instead of master, e.g. python clone.py release-6.0-HF09 -a or something.

From what I can tell, the build process after that is fairly standard Maven that doesn't need too much handholding. I've never had to do a server-upgrade-in-place from the output of this build though (always used the .deb packages), so I don't know the most efficient and correct way to do it. You could just replace all of the app binaries and JARs every time, probably, but I don't think that's what the hotfix function in the Admin UI is doing.

Hopefully someone from Nuxeo can correct anything wrong that I've written.

1 votes

Thanks for the suggestions Steven. Hopefully this will help someone else.