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.

Multi Stage Deploy

brannonk

Hello All,

We are currently testing the community version 2.1.0. To manage our sites we need to be able to deploy to two different file server at different stages.
There was a previous post related to this (http://forums.alfresco.com/viewtopic.php?t=7264), but I have not seen any updates to it.
Our setup is similar where we need to deploy to a specific testing application server before deploying to a final production server.

Has anyone done this? Any help would be appreciated.

Find more posts tagged with

Comments

rdanner

Hello All,

We are currently testing the community version 2.1.0. To manage our sites we need to be able to deploy to two different file server at different stages.
There was a previous post related to this (http://forums.alfresco.com/viewtopic.php?t=7264), but I have not seen any updates to it.
Our setup is similar where we need to deploy to a specific testing application server before deploying to a final production server.

Has anyone done this? Any help would be appreciated.

Are you talking about WCM deployment? If so you can create multiple deployment points (one or more for each environment) I haven't dug in too deep with the deployment configuration to see if you can enforce who can deploy to the different servers

Also, I think the hope is that at some point alfresco can virtualize your environment so that you can leverage the incontext preview. We still have a "staging environment" but I think it is a shame in some ways because we can't take full advantage of WCM and and its transparent layers capabilities.

this might be helpful to you.
http://wiki.alfresco.com/wiki/Deployment#Alfresco_To_File_Server_Deployment

kvc

Once you've reviewed the wiki page Russ noted, a few things to keep in mind:

In the AVM (the repo implementation that stores content in web project), each sandbox is actually it's own independent content repository, where certain repositories (user sandboxes, temporary workflow sandbox used for staged specific versions of assets for review or timed submission and deployment to staging) shared content with other sandboxes (ie, share the current version of assets in staging) via a layered directory (and, of course, can share data with any other repository in any other Web Project and any version of that data - files or directories - via additional layers).

Now, each repository - and each snapshot of a repository - can be incrementally deployed to a remote file-server or snapshot. You can take any user sandbox, any workflow sandbox, any staging sandbox, or any version of a user's sandbox, workflow sandbox, and staging sandbox, and push to wherever you want - easily and efficiently.

Now, in our web app, we give you the option of initiating deployment on the latest snapshot of Staging (and to deploy earlier snapshots, allows you to first revert to make an older version the current version, and then in turn letting you deploy). You can add a custom deploy action to a user sandbox if you want, or you can add deployment as a custom action to be automatically trigger via workflow.

Somewhat infinite in terms of possibilities, though some possibilities require some minor customization of workflow or the GUI. Basically, if you map out a flow of changes, we can ensure a proper organization in terms of sandboxes, deployment, and supporting workflow. Most anything at least from the server should be supported.

Kevin