Site deployment
Most commonly FTP is used to deploy an N2 CMS web site. Since the project is composed of several parts that usually are not part of the site project you need not only to deploy project files but also files used by the edit interface, and optionally the templates pack.
Project files
Use the publish web site command to publish your changes to a local folder. This command will copy aspx and other resources included in your project and any dlls in /bin. These files can be transfererred with your FTP client of choice to your web site's site folder.
N2 files
In addition to these you will need to deploy certain files and folders. These are found in the project directory.
When using N2 core and edit only you'll need to deploy:
When using also using the templates pack you'll need to deploy:
- /App_Browsers
- /App_GlobalResources
- /App_Themes
- /Templates
You don't need to update these files when updating the site project unless you upgrade.
Configuration
Usually you need to update web.config. Hot spots are:
- the connection string
- database flavour
- medium trust related configuration
- security/password/membership providers
Take care not to overwrite the web.config when deploying additional changes and upgrades.
Create a /Upload folder and configure it to allow writes. This is usually achieved through your hosting providers control panel software.
Please revise and update
Troubleshooting site deployment.