Self-hosted version of N1ED
N1ED stores all its files on CDN and pro cloud services as well. This is a strong side of the editor because you always have an updated version without any actions. But sometimes you need to have a plan B against any surprises. The self-hosted version is such tool.
N1ED already guarantees uptime close to 100% and has appropriate statistics for the past year. But for protecting yourself more you can use caching CDN.
You create a busy website where even an hour of downtime can cost you too much. You can have a team who update the website every day and they expect to have all features alive wherever they go into the admin panel of your website.
You can also have hundreds of clients you build and serve websites for. They also expect their website will continue working in case of (for example) any network problems on the side of CDN of N1ED.
Your own CDN server
On the one hand you want to have automatic updates to the new versions. On the other hand you need to have protection against network problems outside of your website.
The solution is to create a server on your side, which will:
- Act as a transparent proxy when N1ED Cloud services are available.
- Act as CDN when N1ED Cloud is not available for some reason.
- Switch between these two states automatically.
Here is the short comparison table of configurations available for you:
Using N1ED Cloud
without a caching CDN
Using N1ED Cloud
with a caching CDN
|Inserting widgets (including custom widget templates)||+||—||+||+|
|Adding new custom widget templates||+||—||+||—|
|Inserting Bootstrap blocks (including custom ones)||+||—||+||+|
|Adding new custom Bootstrap blocks||+||—||+||—|
|Uploading files and images||+||—||+||+|
|Managing and editing your files and images||+||—||+||—|
|Load N1ED configurations||+||—||+||+|
|Edit N1ED configurations||+||—||+||—|
As you can see your own CDN caching server will let you have a failsafe way to load N1ED even N1ED Cloud services are down.
Your staff will be able to load N1ED, edit and save content and use all the features of N1ED except feature to change its configuration (adding new blocks and templates is a part of configuration stored on the server). This is the only limitation, all the other features will work as before.
In order to implement your own CDN caching server, you need to:
Create a server. This server needs to be available only to end users of N1ED. You can order the server on some hosting provider or place it inside your own network. The hardware requirements depends on your usage, but most of cases can be covered the cheapest VDS servers like $5/mo. server of Digital Ocean hoster we recommend as stable. This is equivalent to this configuration: 1 CPU, 1Gb RAM, 25Gb HDD/SSD.
Install Nginx there. Configure it with the config files we provide to you. Please ask for configs N1ED team and we will send them to you and fully help to deploy in case you will have any problems. We can also give you test scripts which can imitate network problems your server will cover from.
Switch your N1ED to use CDN instead of the official CDN. Note: from this line you are responsible for keeping this server updated, alive, etc., inaccurate server maintenance can cause N1ED being unavailable even N1ED Cloud is working fine.
Configure N1ED to use caching CDN
This depends on which N1ED integration do you use. Please choose appropriate item below.
- Open your Drupal control panel and go to the page of advanced N1ED options. This page is available at the URL
- Very carefully fill the field "URL of the cache server" avoiding any mistakes.
For example it can be
https://126.96.36.199/cdn/. Please keep trailing slash. Press "Save".
If your CDN server became broken or down you can clear this field and save again. N1ED will switch to work from the official CDN directly.
The screenshot illustrates Drupal caching CDN configuration for N1ED:
Any other installation
In case you use:
- CKEditor plugin
- TinyMCE plugin
- React integration (based on TinyMCE)
- Snippet integration (based on TinyMCE or CKEditor)
you can just pass a special configuration key to your installation:
Please read according to manual of your integration if you have any doubts on how to pass it. The syntax may differ depending on the type you declare your configuration, but very similar to example above.
Another benefit you can use together with caching CDN is manual choosing a version of N1ED to work with. This is useful when you need to be sure a new N1ED version is OK for you before to use it (we deploy major updates monthly). See more info: Choosing N1ED version.