n2cms
Content
n2cms Home
Getting Started using N2CMS
Deploying N2 to a web server
Deploying N2 to a web server
search
attachments
weblink
advanced
image-effects
image-attributes
Paragraph
Paragraph
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Preformatted
Quote
Bold
Italic
Underline
Colour picker
More colours
Formatting
Strikethrough
Subscript
Superscript
Monospace
Clear formatting
Bullet list
Numbered list
Task list
Outdent
Indent
Align left
Align center
Align right
Page layout
Link
Table
Insert
Insert content
Files and images
Link
Symbol
Emoticon
Markup
Horizontal rule
Insert macro
User mention
Jira Issue/Filter
Info
Status
Gallery
Table of Contents
Jira timeline
Lucidchart Diagrams
Trello Board
Other macros
Page layout
No layout
Two column (simple)
Two column (simple, left sidebar)
Two column (simple, right sidebar)
Three column (simple)
Two column
Two column (left sidebar)
Two column (right sidebar)
Three column
Three column (left and right sidebars)
Find/Replace
Keyboard shortcuts help
You are not logged in. Any changes you make will be marked as
anonymous
. You may want to
Log In
if you already have an account.
<h1><span style="line-height: 1.5;">Deployment Options</span></h1><h2><span style="line-height: 1.5;">Zip deployment vs. NoZip deployment</span></h2><p>The N2 administration area has a large number of files that can be burdensome to deploy over FTP. Furthermore, some hosting environment impose limitations on the total number of files hosted. To eliminate these small resource files, you can deploy a N2.ZIP file containing these resource files. The server will transparently extract this N2.ZIP file and serve the extracted files to clients on demand.</p><p>Caveat: more memory used by the ZIP DLL.</p><h2>Keeping Production and Development Data in Sync</h2><p>Once you deploy in production, you may or may not want to move away from using the default SQLite database engine. Either way, take care not to replace your production database with an older development database! We recommend that you periodically replace the database you use in development with copy of your production database so that you can experiment with your current production data. Your development and production instances of N2 do not necessarily need to be using the same database engine. We recommend that you use the import/export feature in the N2 administration area to first export your site to a file, and then import this file in your production setup.</p><table class="wysiwyg-macro" data-macro-name="note" data-macro-id="e1718880-f035-4713-a4f2-0f773b0166ff" data-macro-schema-version="1" style="background-image: url(https://n2cmsdocs.atlassian.net/wiki/plugins/servlet/confluence/placeholder/macro-heading?definition=e25vdGV9&locale=en_GB&version=2); background-repeat: no-repeat;" data-macro-body-type="RICH_TEXT"><tr><td class="wysiwyg-macro-body"><p>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: <a href="http://n2docs.vxcv.com/Documentation/Troubleshooting/File%20Upload%20Issues.html">File upload issues</a>.</p></td></tr></table><h1>Architecture Options</h1><h2>Single web server configuration</h2><p>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.</p><h2>Multiple web server configuration</h2><p>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: </p><ol><li>Use a file synchronization tool like Bittorrent Sync or Syncthing to keep the N2 application directories in sync.</li><li>Place application files, including the Upload directory, on a file share that is shared across all web servers.</li></ol><p> </p>
Save
Close
Edit
Preview
View changes
Revert to last published version
{"serverDuration": 190, "requestCorrelationId": "b9ddebf2b75a4743a6ff1c2be2a0a307"}