Best way to keep MojoPortal up to date

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

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.

9/25/2011 9:42:03 PM

jnouel

Total Posts 7

View Posts

Best way to keep MojoPortal up to date

Hi,

I'm nearly launching a new web site and I was wondering what would be the best way to keep MojoPortal Source Code updated. I will have some custom modules and they are being developed in seperate projects as per the instructions indicated for the developers.

I understand that we can download the lastest stable source code and work from there. If a new release is made available we just reconfigure everything with the custom project in place as before. Run the setup scripts and that's it.

We also think we can work with the Source Code downloaded from the Mercurial Repository and keep updating it by pulling the changes on a regular basis.

What approach do you recommend? Or is there a better way?

Thanks and regards.

9/27/2011 6:58:51 PM

Jamie E

Total Posts 1203

View Posts

Help support mojoPortal!
Add-on modules

Re: Best way to keep MojoPortal up to date

I deploy from source, with several custom modules, and my typical workflow is the following:

During app development, I download the latest mojoPortal code with TortoiseHG each time before I launch Visual Studio.
I test builds on my local workstation (configured to run IIS), and build/publish/clean/backup target/upload to our development server if I need some collaboration from others for testing.
When a new version of mojoPortal is released, I usually wait a couple of days to see if problems are reported, then notify our webmasters that I am updating the production server. I then download the latest source with TortoiseHG, and build/publish/clean/backup target/upload to both development and production servers. If a problem is identified after I have deployed to production, I run this sequence again once it's fixed in mojoPortal or my own code.

I hope that helps.

Jamie

9/27/2011 7:44:06 PM

jnouel

Total Posts 7

View Posts

Re: Best way to keep MojoPortal up to date

Thanks. That helps a lot.

Cheers!

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