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.

Virtualizing other presentation tiers

sgottlieb

Is it possible to "virtualize" a presentation tier that is not Alfresco based? I see in the sample application that you are able to publish the full WEB-INF directory so it looks like you could publish an entire web application onto a remote server.

Is there any documentation for how publishing works? BTW, when I try to preview the alfresco demo site, I get an empty page. Here it the URL that it is trying to serve: http://www-alfresco-com--staging.avm.127-0-0-1.ip.alfrescodemo.net:8180/ROOT/index.jsp

Find more posts tagged with

Comments

kvc

Is it possible to "virtualize" a presentation tier that is not Alfresco based? I see in the sample application that you are able to publish the full WEB-INF directory so it looks like you could publish an entire web application onto a remote server.

Is there any documentation for how publishing works? BTW, when I try to preview the alfresco demo site, I get an empty page. Here it the URL that it is trying to serve: http://www-alfresco-com--staging.avm.127-0-0-1.ip.alfrescodemo.net:8180/ROOT/index.jsp

Absolutely! An Alfresco Web Project is can manage and virtualize any number of web apps - whether those are using Alfresco services or content or not. In the GA version (working source currently available for
download from our forge site), you'll actually be able to create / delete
web apps within a web project and virtualize even the most complex
of sites.

For deployment, we will be providing an integrated deployment engine
that will replicate assets either to a remote file-server (statically generated
site, non-Alfresco dependent web app) or an Alfresco run-time instance (which will auto-mount the deployed version of the website for all assets to be directly served from Alfresco in run-time - not just content, but also code).

At this point, if you're looking at digger deeper in repository capabilities and config options, I would recommend downloading and compiliing the latest source. There have been enough differences between the Preview and the pending GA codebase that unless you're doing a quick product tour, the Preview release is no longer the best option for you to be digging into.

Let me know if further questions.

Kevin

sgottlieb

Thanks! Very helpful.