This will generate the executable in the folder.

# Clone the repository
git clone https://github.com/ThomasTJdev/nim_websitecreator
cd nim_websitecreator

# Generate and edit the config.cfg accordingly
cp config/config_default.cfg config/config.cfg
nano config/config.cfg

# Compile
nimble -d:release build

# Run nimwc
# (to add an Admin append the arg "newadmin": nimwc --newadmin)
# (to include some standard pages: nimwc --insertdata)
./nimwc

# Login
127.0.0.1:7000/login

User

The "User" can login and see private pages and blog pages. This user has no access to adding or editing anything.

Moderator

The "Moderator" can login and see private pages and blog pages. The user can add and delete users, but cannot delete or add "Admin" users. The user cannot edit JS, CSS and core HTML - only within the pages and blogposts.

Admin

The "Admin" has access to anything.

Blog sorting

In the settings menu you can specify how your blogposts should be sorted, e.g. on modfied date in ascending order.

Blog searching

To only show blogpost with a specific name, tag or category, you have to append the criteria to the URL. It is not possible to combine these.

website.com/blog?name=nim
website.com/blog?category=article
website.com/blog?tags=code

Docker

• Use the Dockerfile as starting point for your NimWC containers.
• You can run the build_docker.sh and run_docker.sh scripts without changing anything to try out nimwc.

Vagrant

• Use the Vagrantfile as starting point for your NimWC VMs.

NGNIX Config

• Use the NGNIX Config file as starting point for your NGNIX Server configuration.

Google reCAPTCHA

To activate Google reCAPTCHA claim you site and server key and insert them into config.cfg.

SystemD

• Use the SystemD Service file as starting point for your NimWC SystemD Services.

Copy the file nimwc.service into /lib/systemd/system/

sudo nano /lib/systemd/system/nimwc.service

Enable auto start of NimWC:

sudo systemctl enable nimwc
sudo systemctl start nimwc
sudo systemctl status nimwc

CI Builds

• YAML Build templates for several Linux Distros (SourceHut).

CrossCompiling, Build for old Linux

Sometimes you may need Build for very very old Linux, like old Centos and Debian Old Stable, from a recent Linux, like new Arch or Ubuntu, heres how you can do it, without a virtual machine with an old Linux to build.

• https://github.com/wheybags/glibc_version_header#glibc-version-header-generator
• https://github.com/phusion/holy-build-box#system-for-building-cross-distribution-linux-binaries
• https://github.com/dockcross/dockcross#dockcross

• Default settings will work Ok on most systems, sane defaults.
• Some settings are kind of technical, you should know some Linux Kernel related stuff.
• Links are provided on the Firejail config page when makes sense.
• You can harden your system even more by tweaking the Firejail config.
• You can always come back to the default settings and it will work Ok.
• Check that Firejail Status at bottom of the page is mostly green.

You can choose how much CPU & RAM NimWC can use, Firejail will make NimWC believe that theres less CPU & RAM that the actually physically available. If you choose too small resources for too big load, then it will feel like when you try to run a heavy program on a VirtualBox with too small CPU & RAM, but will still run, or do the best to try to run. This can be useful for Clouds that charge you extra when you pass certain threshold of CPU & RAM usage.

NimWC does not depend on any Hardware device to run, like audio, video, USB, DVD, etc, so you can block the access to the hardware peripehals, that also blocks its hardware drivers and libraries that may have vulnerabilities, making your NimWC more secure.

There are options to block root user and the rest of the users on the Linux system, thats help protect your NimWC against Privilege Scalations, thats when an unprivileged normal user becomes superuser root, or an user can see other users stuff.

Caches and Temporary directories are mounted as private temporary unique autogenerated TMPFS, meaning that the real ones can not be altered from within NimWC.

noMnt=true is for when you run 1 instance NimWC per server, noMnt=false is for when you run multiple instances NimWC per server, because it may or may not block other instances of accesing subfolders on /mnt/ simultaneously.

noX=false if you are running a headless server or ChromeBook. noX=true uses Xvfb for X Isolation (xorg-server-xvfb), you may need to install it if you want to use it, but is not a hard dependency, just use noX=false and you dont need to install it if you dont want to.

The features come from the Linux Kernel itself, so theres zero cost on performance and the technology is already there even if you use it or not.

So in conclusion NimWC being compiled binary wont need access to most of your system, just its own folder, the integration with Firejails hides everything else.

Install

You local version of firejail to needs be >= 0.9.58. Install using your package manager:

# Arch (package manager)
sudo pacman -S firejail

# Ubuntu (built files)
https://launchpad.net/ubuntu/+source/firejail/0.9.58-1 # <-- download
sudo apt install ./firejail_0.9.58-1_arm64.deb

# Compile
git clone https://github.com/netblue30/firejail.git
cd firejail
./configure && make && sudo make install-strip