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.

publishing to external webserver

dpatri

Maybe I am not understanding this correctly, but how to set up WCM to publish to an external webserver? I understand the user sandboxes and the staging box. But they are both within Alfresco. How would one publish to a production website? In my case, the requirement is pretty simple, they are just static webpages on an apache server, that I am hoping to maintain with Alfresco.

Find more posts tagged with

Comments

steve

Hello,

A 'push' publishing tool is a goal for the 2.1 release.
For the 2.0 release, you can use FTP or CIFS to pull the data from Alfresco to the Apache web server.

Hope this helps,

Steve

dpatri

Steve,

Thanks. It does. I will look for alternatives like FTP or CIFS, perhaps in an automated fashion.

The main issue with such a way is, short of refreshing the whole site each time an update is made, I would have to maintain the syncing (like when a file is modified, or when a file is deleted).

Refreshing the prod site each time is ok, if it is a small site, but a large site with lots of html files and images could prove problematic.

I look forward to this functionality in 2.1. Keep up the good work!

kvc

Please note: our deployment capabilities are scheduled to ship with our 2.0.1 enterprise maintenance release. The RQA build is currently available on the Alfresco Content Community for community members to get early access to assist in our testing efforts. Please see that earlier announcement on the WCM forum:

http://forums.alfresco.com/viewtopic.php?t=5949

Kevin