Deployment Options
Zip deployment vs. NoZip deployment
...
Caveat: more memory used by the ZIP DLL.
Single web server configuration
The simplest option is to deploy N2CMS to a single web server. You can achieve higher scalability and resilience by using a 3rd party solution such as Cloudflare to provide high availability and CDN caching.
Keeping Production and Development Data in Sync
...
| Note |
|---|
If the file is very large, you might not be able to upload the file to your development instance unless you change some configuration settings. See the related topic: File upload issues. |
Architecture Options
Single web server configuration
The simplest option is to deploy N2CMS to a single web server. You can achieve higher scalability and resilience by using a 3rd party solution such as Cloudflare to provide high availability and CDN caching.
Multiple web server configuration
When using N2CMS with multiple web servers, all instances of N2CMS should share the same database and content files. You will also need to keep the site files in sync between all servers. There are two main options here:
- Use a file synchronization tool like Bittorrent Sync or Syncthing to keep the N2 application directories in sync.
- Place application files, including the Upload directory, on a file share that is shared across all web servers.