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; } } }

Livesite Staging Instance?

k1DBLITZ

We currently have a dev and production environment which consists of a dev teamsite server, a dev livesite server, and a prod teamsite server and a prod livesite server.

We now have the need for a livesite staging server.

I would like to spawn another Livesite instance on the dev livesite server.

This instance would run on port 1778 and serve content from a "sites-staging" root folder.

Can anyone point me in the right direction?

Find more posts tagged with

Comments

nipper

This is a tad confusing. Is this a new server or a new site on an existing server ?

k1DBLITZ

This is a tad confusing. Is this a new server or a new site on an existing server ?

My apologies, I'll try to be more concise.

We have a dev server in the webDMZ that is running Livesite. We are using the default root folder to serve content which is:

\Interwoven\LivesiteDisplayService\runtime\web\sites

In that dir is a folder for each website that is being hosted, for example:

website1
website2
website3
website4

On this same physical server, I would like to spawn a "staging" instance of Livesite, listening on a different port, and serving content from a different webroot, something like:

\Interwoven\LivesiteDisplayService\runtime\web\sites-staging

website5
website6
website7
website8

Is this possible?