History

mike12345567 464f973f12 Adding a separation for MariaDB and MySQL, mariaDB is the core of the problem, this solves for it by separating them and allowing us to use the special json_arrayagg for mariaDB, but use a correlated sub-query for MySQL.		2024-09-24 12:01:47 +01:00
..
__mocks__	Merge branch 'master' of github.com:budibase/budibase into test-oracle	2024-08-02 11:20:19 +01:00
build	…
scripts	Defaulting SQS to on in development environments, this removes the need for setting it in the management scripts.	2024-08-30 15:10:55 +01:00
specs	…
src	Adding a separation for MariaDB and MySQL, mariaDB is the core of the problem, this solves for it by separating them and allowing us to use the special json_arrayagg for mariaDB, but use a correlated sub-query for MySQL.	2024-09-24 12:01:47 +01:00
.dockerignore	…
.gitignore	…
.npmignore	…
.yarnrc	…
Dockerfile	updating budibase apps image to use alpine	2024-09-11 17:42:08 +01:00
LICENSE	…
README.md	…
babel.config.js	…
datasource-sha.env	Revert to testing against mssql 2017, attempt to get relationship aggreggation working.	2024-09-04 16:21:32 +01:00
docker_run.sh	…
jest.config.ts	…
nodemon.json	…
package.json	merge	2024-09-20 17:39:19 +01:00
pm2.config.js	…
tsconfig.build.json	…
tsconfig.json	…

README.md

Budibase server project

This project contains all the server specific logic required to run a Budibase app

App migrations

A migration system has been created in order to modify existing apps when breaking changes are added. These migrations will run on the app startup (both from the client side or the builder side), blocking the access until they are correctly applied.

Create a new migration

In order to add a new migration:

Run yarn add-app-migration [title]
Write your code on the newly created file