CodeMirror/budibase
1
0
Fork 0
mirror of synced 2024-06-28 02:50:50 +12:00
Code Issues Projects Releases Wiki Activity

Merge branch 'master' of github.com:Budibase/budibase

Browse source
This commit is contained in:
Martin McKeaveney 2020-07-15 13:51:33 +01:00
parent 3fbf3f4826 9009b675b0
commit 0d0ffeb530
5 changed files with 27 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
CONTRIBUTING.md
View file

@ -149,7 +149,25 @@ The backend schema, models and records are stored using PouchDB when developing
### Publishing Budibase to NPM
You can publish all the latest versions of the monorepo packages by running:
#### Testing In Electron
At budibase, we pride ourselves on giving our users a fast, native and slick local development experience. As a result, we use the electron to provide a native GUI for the budibase builder. In order to release budibase out into the wild, you should test your changes in a packaged electron application. To do this, first build budibase from the root directory.
```
yarn build
```
Now everything is built, you can package up your electron application.
```
cd packages/server
yarn build:electron
```
Your new electron application will be stored in `packages/server/dist/<operating-system>`. Open up the executable and make sure everything is working smoothly.
#### Publishing to NPM
Once you are happy that your changes work in electron, you can publish all the latest versions of the monorepo packages by running:
```
yarn publishnpm
@ -157,6 +175,10 @@ yarn publishnpm
from your root directory.
#### CI Release
After NPM has successfully published the budibase packages, a new tag will be pushed to master. This will kick off a github action (can be found at `.github/workflows/release.yml`) this will build and package the electron application for every OS (Windows, Mac, Linux). The binaries will be stored under the new tag on the [budibase releases page](https://github.com/Budibase/budibase/releases).
### Troubleshooting
Sometimes, things go wrong. This can be due to incompatible updates on the budibase platform. To clear down your development environment and start again:

2
packages/cli/package.json
View file

@ -29,5 +29,5 @@
"uuid": "^7.0.3",
"yargs": "^14.2.0"
},
"gitHead": "4a7edd9ebe702c93e8b9da2b74e814d3bb1266e1"
"gitHead": "eff4fa93ca1db11b97b5fdedc0c488413e277eb8"
}

2
packages/materialdesign-components/package.json
View file

@ -52,7 +52,7 @@
],
"version": "0.1.8",
"license": "MIT",
"gitHead": "e4e053cb6ff9a0ddc7115b44ccaa24b8ec41fb9a",
"gitHead": "eff4fa93ca1db11b97b5fdedc0c488413e277eb8",
"dependencies": {
"@material/card": "4.0.0"
}

2
packages/server/package.json
View file

@ -95,5 +95,5 @@
"./scripts/jestSetup.js"
]
},
"gitHead": "4a7edd9ebe702c93e8b9da2b74e814d3bb1266e1"
"gitHead": "eff4fa93ca1db11b97b5fdedc0c488413e277eb8"
}

2
packages/standard-components/package.json
View file

@ -35,7 +35,7 @@
],
"version": "0.1.8",
"license": "MIT",
"gitHead": "e4e053cb6ff9a0ddc7115b44ccaa24b8ec41fb9a",
"gitHead": "eff4fa93ca1db11b97b5fdedc0c488413e277eb8",
"dependencies": {
"@beyonk/svelte-googlemaps": "^2.2.0",
"fusioncharts": "^3.15.1-sr.1",