Skip to content
Branch: master
Go to file

Latest commit


Failed to load latest commit information.
Latest commit message
Commit time


Join the chat at Semver

What exactly is SHPS?

SHPS is a homepage management system which assists you with making a homepage or web application in general! SHPS comes as a core system (no Admin GUI or additional features) which can be extended with many useful plugins. Plugins are what make SHPS special. They are very separated from your site, but can be integrated seemlessly into your site with exactly the theming and placement you need and want. Plugins can be anything; a forum, a blog, analysis tools for admins,...

  • Security is a big point and SHPS tries to automatically make your software save from hackers.
  • SHPS is fast and tries to limit resources. We are constantly working on the algorithms to improve their calculation and transfer speed - every millisecond counts!
  • No matter, if you make a small website or a huge MMORPG, SHPS always tries to be scalable.
  • SHPS defines a rough way of splitting your big problem into many trivial ones.
  • SHPS adds a huge set of helpful functions, like user/rights management.
  • Making software portable by making you as a developer independant from the OS, web server and even database is a thing we are working on
  • SHPS is opensource since we want to gain your trust. Only a well informed community will help make SHPS big.
  • Easing the process of making rich Web Applications is a major aim of SHPS

This is only a very rough feature set and the principles SHPS is based on. Please take a look at the detailed feature overview and download SHPS for free to test it out. Build your site with SHPS and see if it fits your needs. If your project is non-commercial, SHPS is completely free as in gratuit, but always consider giving us a small donation as we put a lot of money and time into improving SHPS every day :)

TODO List (not ordered) for under-the-hood improvements (wouldn't really call them features)

  • move TODO list to github's open issues (make branches/forks and a resulting pull request for each issue)
  • GUI. Let's be honest, a GUI is a game-changer and will make SHPS accessible for more people and especially beginners
  • work on feature list
  • add config-tester which is called on startup and implements a modular test-interface for checking stuff like DB connections ahead
  • implement domain/user-states which cache certain objects (e.g. log, auth, permissions-array,...)
  • only load plugins which are enabled by configurations
  • only use explicitly enabled plugins for defined requests
  • improve logging capabilities
  • guided setup
  • make init module for all startup action
  • include dependency checks into init flow
  • add config file encryption (I think this is a ASVS item... but this will be hard to implement as SHPS should be able to auto-start...)
  • add ipc in local cluster to improve collaboration between processes
  • improve cluster-collaboration by assigning specific tasks to different processes
  • add possibility of npm-modules which are loaded as plugins
  • add auto dependency installation (e.g. download openssl/libressl binaries and install them next to SHPS if missing)
  • improve sandbox security (omfg, this will be a never-ending item)
  • better error detection and management
  • improve HTTPS security
  • stabilize HTTP/2 server
  • certificate based login
  • improve commandline
  • cache requestState cached structures
  • re-enable gzip compression
  • cache DB in local variables on startup; add cache-tools to commandline in order to invalidate cache manually
  • enable site-specific plugin (interesting for plugin version as well) by adding subdirectories to /system/plugin
  • check if plugin is loaded or physically available before trying to use it (e.g. calling event)
  • setup plugin repository and add plugin-commands for console (and extend plugins module so it can download and install plugins; from code as well for plugins and GUI :) )
  • add better mimeType management and auto-detection
  • process client hints
  • plugins should get their own namespace in node-mod-load (see node-mod-load issue #5)
You can’t perform that action at this time.