Hi Nathan,

I used to use GoDaddy but swapped because I found it much more hassle than it should be to get a good working practise for MojoPortal.

I now have a setup where its trivial to swap between my local environment and hosted environment (just a couple of button presses) and I have better control of my remote database. Correct me if I'm wrong, but I'm pretty sure Go Daddy do not support Web Deploy, which in particular makes copying SQL databases between local & remote a breeze (its all done for you).

I used the hosting page on this (the MojoPortal) website and setup an account with Arvixe, and have been very pleased since then. I also find them way better value.

For reference, there's a series starting on creating a local / remote environment here.

Take it easy,

Spike

Hi Joe,

I do agree with what you say. I wouldn't overwrite a live deployed database.

I do, however, find it important to be able to very easily copy my live site to my local pc for testing (particularly while I'm still learning MojoPortal).

My sites are currently mainly in the state 'deployed for testing'. If I see or am notified of a bug, I want to be able to get my deployed site (including data) copied on to my local environment (or test published environment) with minimum hassle to make debugging easier. Being able to select 'download published site', unselect a config file then press go works for me. I expect this to be more important if/when I get developing in visual studio.

I also like being able to move my published site really easily if I want to.  Again I use this for testing to take a snapshot of the live site, copy it to a test published environment so someone can test a particular part of the site.

I dare say it could also be done by backing up, downloading and restoring databases, but this way its all done in one go.

When I create a new site, I initially make it local. When its working & ready to be deployed, publishing is pretty much a one button press affair.

If I want to do a major update, I may want to do that locally then publish it, but would have to take the deployed site offline while doing that.

and its not a typica medium troust there sql strings are a pain in the but if you dont know what your doing took me 3 days firt time to do godaddy for mojo but now 30 secs like i said there hosting config is a nightmair

Nathan - I'm not a big fan of GoDaddy, but if you'd like to do a write-up, the folks who are using GoDaddy would probably appreciate it. Every hosting environment has different strengths and weaknesses.

There are multiple ways of setting up a MojoPortal project for development, based on whether or not you're leveraging source code or the web install version.  I'll write up some steps for setting up a source code development/deployment scenario over on the Arvixe blog later today, but I'll break it down into a multi-part, with the hosting-agnostic in the first part. Thanks!