nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

3.5.a community linux installation file

bweinberg

I am not certain if this is the correct place to post this, but I am interested in trying Alfresco Community Edition 3.5.a. However, the linux installer (i.e. alfresco-community-3.5.a-installer-linux-x64.bin) is missing from the nightly builds. Is this by design, or is this an oversight. Any feedback would be appreciated.

Brian

Find more posts tagged with

Comments

mrogers

http://forums.alfresco.com/en/viewtopic.php?f=8&t=38473

bweinberg

Thank you for your reply. Typically (at least going back the past year or two), nightly builds has included the installers for both linux and windows distributions. That said, if that practice has changed, it might be useful to note that somewhere in the nightly builds, that's all.

I think having the installers in the nightly builds should be important for project development. Although I have built Alfresco piecemeal in the past, the installers certainly provide a much easier way to get a test bed up and running quickly. In fact, I have found that since Alfresco CE changed to a more complete installer package a while back (including all the necessary required dependencies), not only is it easier to build a test bed, but it helped eliminate quirks caused by variations otherwise made by custom installations. I found this to be particularly true in the linux build, as various distributions of linux, as well as different versions of each distribution, would often include versions of dependent software which worked less effectively than the versions included in the community installers.

I would imagine that eliminating problems/bugs in software as sophisticated as Alfresco must be easier when the vast majority of installations are built using a unified stack, as opposed to determining where problems arise as a result of various custom installs.

For the record, I love Alfresco, and the engineers and the community should all be commended on doing a wonderful job.

Just my two cents.

mrogers

Thank you for your comments. I suspect that the missing installers are more by accident than design.

The installers tend to be the last thing developed, so are often not available until really late in the development cycle.

Alfresco is quite easy to install without the installer once you know what goes where and why.