new publish

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.
3/3/2015 12:07:53 AM
Gravatar
Total Posts 27

new publish

I have a published version of my code on my server, and a source code on my pc. The end users are already working on the published version. I have done some modifications on my source code. I have issued a new published version and I need to update the published version on my server with the new published version. But I dont want my end users to lose their work. Beside the database and the Data folder, what else do I need to keep before copying the new published version on the server?

3/3/2015 9:49:08 AM
Gravatar
Total Posts 1188
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

Re: new publish

Here's my general workflow when upgrading:

  • TortoiseHG pull to make sure local code base is completely up-to-date.
  • Make sure all purchased add-on products are up-to-date in the local code tree.
  • Rebuild All.
  • Publish from Visual Studio to a local folder.
  • Verify that \Data\Sites\* is not included in the published folder; delete it if it is.
  • Delete unneeded multilingual translation, help, and message template files from the published folder.

For the following steps, I start with our development web server first, then notify users and give them time to test. Once testing has been completed and everyone is ready, I perform the same steps to the production server.

  • Stop web site; back up file tree and database.
  • Copy the local published folder over the top of the root of the web site mojoportal folder, overwriting all files.
  • Start the web server.
  • Navigate to /setup.aspx.
  • (optional) Delete any older versions of 3rd party products (CKEditor, TinyMCE, etc.) from the web server.

One thing I don't show here is the need to make sure your local web.config is appropriate for production use. I always keep the local web.config production-ready, so I don't have to worry about modifying it during deployment.

I hope that helps,

Jamie

3/20/2015 11:50:17 AM
Gravatar
Total Posts 55

Re: new publish

Jamie, 

Great advise.. I printed this off and hung it on my wall right above the development machine..

Thanks for your support..

 

Joe

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