Hi, i start currently create and develop a website with umbraco 7.x on lokal development pcwith windows 7, visual studio 2013 and sql server express 2008.
Later i will deploy the created website page on Windows Server 2012 and SQL Server 2012 and installed umbraco 7.x.
Whats the best practice to handle this? best regards axel
1: Script your database and import it in your SQL server 2012 instance - Unless you're going to make some custom database stuff you don't need to think about this when extending the site. Otherwise you will of course need to script and deploy new tables as you develop, but be carefull not to overwrite any Umbraco tables since you don't want to mess up the content from your live environment
2: Copy your files to the webserver and make sure your IIS website is pointing to the correct folder and that bindings etc. has been added as well. Also make sure that permissions has been properly set up. You could use a FTP client for this.
When you need to update file changes you can copy files/folder that has been changed.
You can also have a look at the umport package, which should make deploying easier.
The above is basically what you need to do - depending on your setup you can probably optimize/automate some of it using grunt to copy files from dev to live for instance.
You could also have a look at the commercial Courier package developed by Umbraco HQ to make deploying easier. But be aware that it can sometimes cause some issues due to 3rd party packages etc. - So depending on what you're doing this package might be overkill.
Develop lokal ,deploy later on production Server
Hi, i start currently create and develop a website with umbraco 7.x on lokal development pcwith windows 7, visual studio 2013 and sql server express 2008.
Later i will deploy the created website page on Windows Server 2012 and SQL Server 2012 and installed umbraco 7.x.
Whats the best practice to handle this?
best regards axel
Hi Axel
Basically what you need to do initially is
1: Script your database and import it in your SQL server 2012 instance - Unless you're going to make some custom database stuff you don't need to think about this when extending the site. Otherwise you will of course need to script and deploy new tables as you develop, but be carefull not to overwrite any Umbraco tables since you don't want to mess up the content from your live environment
2: Copy your files to the webserver and make sure your IIS website is pointing to the correct folder and that bindings etc. has been added as well. Also make sure that permissions has been properly set up. You could use a FTP client for this.
When you need to update file changes you can copy files/folder that has been changed.
You can also have a look at the umport package, which should make deploying easier.
The above is basically what you need to do - depending on your setup you can probably optimize/automate some of it using grunt to copy files from dev to live for instance.
You could also have a look at the commercial Courier package developed by Umbraco HQ to make deploying easier. But be aware that it can sometimes cause some issues due to 3rd party packages etc. - So depending on what you're doing this package might be overkill.
Hope some of these pointers help.
/Jan
is working on a reply...