I have a dedicated server where I could self host buzztouch. Some questions about it: 1. Will I have the latest version as if I create apps on the website version? 2. Does it auto-upgrade, or how is the process of getting the latest version? 3. Can I move my projects from the website to the self-hosted option? 4. Will I be able to go back from self-hosted to the website if I choose to do so (unlikely but just want to know)

Some good questions - here's some thoughts... 1) You'll have the latest version of the main source code package each time you download it for an app. You may or may not have the latest version of plugins that get downloaded - those have to be manually updated on your server. 2) When a new version gets released, David makes an announcement on the forums and a link to the software with instructions. 3) No, you'll have to recreate them 4) Yes, but like #3, you'll have to recreate the apps on buzztouch.com

It's worth it though!

thanks! you say "When a new version gets released, David makes an announcement on the forums and a link to the software with instructions". Can you share a link where I can see what's involved for upgrading?

Installation and Upgrade of the Buzztouch package is no more involved than an installation or upgrade of most 'content management systems' such as joomla or wordpress. If you have any experience with those, this won't be an issue. If you have no experience, you'll need to know how to create a MySQL database, and create credentials to use with your BT Server configuration. You'll need the names or IP Addresses of your resources, things like that. What's usually involved in an upgrade is backing up your server data (although it rarely gets touched) and copying the new files to your server. Usually via File Transfer Protocol (F.T.P.). You may be able to find self hosting links, but you may not; You're not a member yet so If you can't find them, then you probably have to be a member to 'see' them. The only time I've seen the 'BT Server' more recent than self hosted servers was during the 'PUSH' messaging release earlier this year. Naturally David wanted to work out all the kinks before he released it publicly, so the BT server was implemented a few weeks ahead of the Self Hosted Version. Plugin updates are manual, but it's just basically a 'two button' push process; one to sync your plugins with those available in the BT Market (and updating as needed) and another to 'refresh' the plugin information so the system is aware. If you're going to use the BT Control panel and then later migrate to Self Hosted, the only advice I can see being really advantageous, is either: 1) Get 'real' familiar with Stobe's JSON Snippet keeper... and 2) Whenever possible, always use a childItem file rather than entering a million entries in the control panel, and having to recreate them in self hosted. With a childItem file, you can embed it into your app, so there is no performance hit (or you can have them available online, and the only performance hit you'll get is the initial download; afterwards it's cached). You also won't have to re-enter all that data. Especially if you have a quiz with a few hundred questions. Just my 10 yen. Cheers! -- Smug

thanks, I'm very familiar with WP and Joomla. For WP you can upgrade with the touch of a button, 3 seconds and you're done. But for Joomla is a pain in the a..s. They have a very complicated process for upgrading the CMS. What I understand is the upgrade in BT is manual (backup, copy files, etc) and not as simple as WP. How frequent are the updates?

Updates are pretty infrequent. My guess is we'll eventually get to the point of a single-button update process. But we're not there yet.

I can say it's not as hard updating BT as it is Joomla. I'm still trying to figure out how to gracefully update (on my hosting service) from 1.7.3 to 2.5.x, lol! It really wasn't hard updating my BT Server though. I backed up my SQL Database, I made a copy of my 'files' directory (which was really unnecessary, but I'm picky about that sort of thing...) and ran through the update script, which was basically the install script again. Double check your config file, and enter some new data (for like, the app usage map, etc...) and you're done. Believe me, it may not be 'one button' (yet), but it's really no big deal. And like Chris said; updates come infrequently, and I'm sure eventually, like the plugins, it'll be one button or less to update. Until then, some assembly required, but not much. Cheers! -- Smug

Thanks guys! (by the way, Smug, after researching what would be the best option for upgrading our Joomla sites we decided to go with a free plugin called jUpgrade. We'll still need to change templates and upgrade components, but see if it helps).

It's the components, I have a million I need to find updates for. I've got Jplugin... I just have a bunch of prep to do. Never put off until tomorrow what you can put off until next week. ;) Cheers! -- Smug