cancel
Showing results for 
Search instead for 
Did you mean: 

Production URL?

grumpy_burton
Champ in-the-making
Champ in-the-making
Hi there,

I've got a rather silly question to ask… what is the "Production" URL that should be used for delivering a WCM Web Project? Should a seperate sandbox/virtual server be set up for it? or does it run off the main alfresco context?

* Alfresco
e.g. http://127.0.0.1:8080/alfresco

* Production
e.g. ???

* Preview Sandbox(s)
http://myDNIS.www-sandbox.127.0.0.1.ip.alfrescodemo.net:8180/

* User Sandbox(s)
http://admin.myDNIS.www-sandbox.127.0.0.1.ip.alfrescodemo.net:8180/

Cheers,
Alex.
4 REPLIES 4

jcox
Champ in-the-making
Champ in-the-making
See the wiki article on configuring the virtualization server:

    http://wiki.alfresco.com/wiki/Configuring_the_Virtualization_Server

   Cheers,
   -Jon

grumpy_burton
Champ in-the-making
Champ in-the-making
Ok, So just to confirm, I should be setting up a virtualization server for the final production site?

i.e. http://www.mydomainname.com:80

jcox
Champ in-the-making
Champ in-the-making
The URL you should generate depends upon what you
want your production environment to be like.

In all cases though, I suspect that the intention of a
"production" environment  includes allowing people
who are not running their browser on the same  box
as the virt server to see virtualized content.

Assuming this is the case, and assuming your
you are serving content directly out of an Alfresco
repository, you do not want to the loopback address
to appear in hyphen-encoded form within your URLs
( xyz.127-0-0-1.ip.alfrescodemo.net ).

Again, please read the wiki page:
http://wiki.alfresco.com/wiki/Configuring_the_Virtualization_Server
All of this is explained there.

If there is a particular sentence within this wiki page that
you are having trouble understanding, or if specific parts
seem vague or lacking in examples, let me know and
I'll clarify it for you (and everyone else).   Be as specific
as possible, so I can be sure to address your needs.

You are not  even required to serve content directly out of an
Alfresco repository in your production server. Alfresco is a highly
layered & configurable  system.   Exactly what your URLs should
look like depends on your goal, the hosting environment, the
features & performance requirements, whether you have any
reverse proxies in your stack, whether the users in production each
need their own virtual space, and so on.  There is no one
"production" environment style of URL, instead it will reflect the
design choices you've made overall (the same goes for deployment).

  I hope this helps,
  -Jon

eyestreet
Champ in-the-making
Champ in-the-making
Hey Grumpy, and Jon,

I've seen over the years that most "production" instances of a web site are run in a segmented/partitioned environment, that is separate from your content development environment.  With Alfresco there are actually two (2) ways to accomplish this.

The first way would be to copy the Alfresco runtime repository (AVM) out to your production web stack, and either map directly into it via CIFS (with your web app server), or to use the AVM api to gain access to the content you want to deliver.

The other option would be to extract the content from your staging area (or wherever you agree is the content that is golden and ready to be seen by the public) to a directory structure that your production web application server can see.  You can use CIFS and a file copy application (FTP, SFTP, SCP, etc).  We (Eye Street) have also developed a content deployment mechanism that will deploy from one server to one or more servers.

I hope this helps!

Brent Kastner
Eye Street