Deployment

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
7/4/2008 10:52:01 AM
Gravatar
Total Posts 10

Deployment

Hi,

Which is the best way to deploy mojoPortal based website.

I quickly need to deploy my case study website

7/4/2008 11:36:30 AM
Gravatar
Total Posts 18439

Re: Deployment

Hi,

The best way in my opinon is first pacakge your build in a local folder using UnLeashIt as described here:

http://www.mojoportal.com/deploymentfromwindows.aspx

Then upload to your hosted environment or production machine.

Note that I do not recommend populating your database on one machine and then moving it to another machine. It can be done by restoring a db onto another machine but if your relative urls have changed then you will have problems with broken links. Better to use a different db for deveopment than for production. Create production content and pages right on the production machine not on development. So, in other words after deploying your build on production for the first time, then visit /Setup/Default.aspx to complete the installation same as you did on development.

Hope it helps,

Joe

You must sign in to post in the forums. This thread is closed to new posts.