Name		Name	Last commit message	Last commit date
Latest commit History 198 Commits
.github		.github
.husky		.husky
data		data
scripts		scripts
src		src
.dockerignore		.dockerignore
.env.example		.env.example
.eslintignore		.eslintignore
.eslintrc.js		.eslintrc.js
.gitignore		.gitignore
.lintstagedrc		.lintstagedrc
.prettierignore		.prettierignore
.prettierrc		.prettierrc
LICENSE		LICENSE
Makefile.dev		Makefile.dev
README.md		README.md
docker-compose.dev.yaml		docker-compose.dev.yaml
dockerfile.dev		dockerfile.dev
jest.config.base.js		jest.config.base.js
jest.config.integration.js		jest.config.integration.js
jest.config.unit.js		jest.config.unit.js
package-lock.json		package-lock.json
package.json		package.json
tsconfig.json		tsconfig.json

Repository files navigation

Cridium Server

Backend implementation of Cridium built with DeepKit.

WIP: missing features and not ready for deployment.

git clone https://github.com/Cridium/cridium-server.git
cd cridium-server
npm install
cp .env.example .env

npm run app would bootstrap the application without any further instructions, which would print a list of CLI commands available in the application. You can follow the printed information to run certain commands like npm run app migration:create.
npm run dev would start the application as a server and watch file system changes in the workspace for developing.

Because of some known issues of the current release of DeepKit, some features are temporarily not available:

When enabling APP_FRAMEWORK_DEBUG, the ORM part of the DeepKit Debugger is not available.
Database related features like APP_FRAMEWORK_MIGRATE_ON_STARTUP and npm run app migration will not work as expected. (thus the server will not work properly without manual database migrations)