pxslip / db-studio Goto Github PK

View Code? Open in Web Editor NEW

This project forked from lawebcapsule/directus9

0.0 0.0 0.0 205.54 MB

A fork of directus v9, predates the shift to BSL remaining true FOSS.

License: GNU General Public License v3.0

JavaScript 0.68% TypeScript 68.58% CSS 0.18% HTML 0.03% Liquid 0.36% Vue 29.18% Dockerfile 0.02% SCSS 0.97%

db-studio's Introduction

DB Studio (Formerly Directus v9)

Introduction

DB Studio (Formerly Directus v9) is a real-time API and App dashboard for managing SQL database content.

Free & open-source. No artificial limitations, vendor lock-in, or hidden paywalls.
REST & GraphQL API. Instantly layers a blazingly fast Node.js API on top of any SQL database.
Manage pure SQL. Works with new or existing SQL databases, no migration required.
Choose your database. Supports PostgreSQL, MySQL, SQLite, OracleDB, CockroachDB, MariaDB, and MS-SQL.
Completely extensible. Built to white-label, it is easy to customize our modular platform.
A modern dashboard. Our no-code Vue.js app is safe and intuitive for non-technical users, no training required.

JS SDK

A JS sdk is also realeased under @db-studio, you can install it via:

npm install --save @db-studio/sdk

Extensions

All classic Directus version 9 extensions should work without changes on DB Studio.

When developing a new extension for DB Studio (Formerly Directus v9), you should use the latest version of @db-studio/create-extension to scaffold:

npm init @db-studio/directus-extension@latest
# or
pnpm create @db-studio/directus-extension@latest
# or
yarn create @db-studio/directus-extension@latest

License

DB Studio (Formerly Directus v9) is released under the GPLv3 license. Monospace Inc owns all Directus trademarks, logos, and intellectual property on behalf of our project's community.

db-studio's People

Contributors

db-studio's Issues

FEAT: Improved Time Series Charts

A user is able to mark periods of time on the x-axis, e.g. mark 1945-1960 and 1960-1980 etc. with lines on time chart or with different background colors.

CHORE: Replace the storage drivers with `unstorage`

unstorage is a well-supported storage driver solution that may be able to be used in place of the custom storage drivers.

FEAT: Pie Charts

A user can create pie chart widgets for the data insights dashboard

FEAT: Handle database table prefixes

The current installation script uses the directus prefix for application tables. It would be nice to 1. have a prefix that is configurable at install time, and 2. have a migration from the directus prefix (or conceptually any other prefix) to a new one.

Issues I can think of with this:

Where to store the prefix? Environment is the easiest, but what happens if a user changes that variable? That would break the application. Maybe copy the prefix to a file somewhere in the application directory structure?
How to migrate existing tables? Need to create table, copy contents, delete old tables. Can you CREATE TABLE table_name with a select?

An interesting side effect is that you could theoretically have multiple application instances sharing a database, just with different app table prefixes. One thing to keep in mind - do the collections table need prefixes at that point?

IMP: Nested Related Data no longer displays in the ancestor form

GrandParent --> Parent --> Child

In the Grandparent form, the data from Child shows as --

Stacked Bar Charts
Clustered Bar Charts