Discords.com
  • Welcome
  • โš›๏ธIridium Engine
    • ๐ŸŽ“Introduction
  • FypFans
    • ๐ŸŽ“Introduction
    • ๐Ÿ—ฃ๏ธChat tools
  • ๐Ÿค–Discords.com Bots
    • ๐Ÿ–จ๏ธReceiving webhooks
    • ๐Ÿ”ขUpdating server count
    • ๐Ÿ”ขGetting bot's upvotes
Powered by GitBook
On this page
  • Basic information
  • Hardware requirements (minimum)
  • Routing system
  1. Iridium Engine

Introduction

Iridium Engine is a Node.JS based request handler designed for optimal performance of our applications.

PreviousWelcomeNextIntroduction

Last updated 1 year ago

While available for the public eye to see, this documention will probably not be useful for the average user/developer as it only describes the functionality of the Iridium Engine system and does not provide information on public facing API routes.

This documentation does not provide insight on security as it is served on a need-to-know basis.


Basic information

Current release (name):

Ionite

Current release (version number):

1

Current release (revision number):

0

Current release (patch number):

8

Current release:

Iridium Ionite v1.0.8

Version in development since:

Apr 6, 2022

Release authors:

Jakub Lukeลก

Node.JS runtime:

NodeJS v16.X.X or higher

Supported systems:

Linux, MacOS X, Windows (opt. WSL)

Optional stack:

MariaDB, Redis, RethinkDB, PostgreSQL, Angular

Hardware requirements (minimum)

CPU:

Broadcom BCM2711, Quad core Cortex-A72 (ARM v8) 64-bit SoC @ 1.8GHz

RAM:

128mb or greater (vacant)

GPU:

Not required

Connectivity:

Not measured

Multi-threading:

Optional

Disk space:

5GB

SSD:

Not required


Routing system

Iridium creates routes based on their filesystem structure. All routes are gathered from the routes folder upon engine startup. As of version 1.0.8, mid-run refreshing is not possible.

Engine startup time varies between devices. Startup will be faster if the engine has run recently. First-time startup usually take up to 90s, lightweight instances up to 10s. Re-runs vary from 1s to 5s.

โš›๏ธ
๐ŸŽ“
Startupoutput, some data redacted
Routing structure example