English | 中文
ODC has a centralized deployment web version and a locally run client version. The web version requires ODC Server to run, while the client version automatically installs the corresponding dependencies and generates a standalone installation package.
After packaging the ODC Server Jar file, store it in the following directory: Build Jar
libraries
- java
- odc.jar
- plugins
- plugin-related packages
- starters
- starter-related packages
pnpm run prepack jar
# Use ODC provided JRE
pnpm run prepack jre
# Use ODC provided OBClient
pnpm run prepack obclient
pnpm install
Modify the proxy
field in config/config.js
and change the target
attribute to the address of the ODC Server.
proxy: {
'/api/v1/webSocket/obclient': {
target: 'ODC Server Address',
ws: true,
},
'/api/': {
target: 'ODC Server Address',
},
'/oauth2/': {
target: 'ODC Server Address',
},
'/login/': {
target: 'ODC Server Address',
}
}
pnpm run dev
This will start a web server on the default 8000
port. Access http://localhost:8000 to open ODC.
ODC client is developed based on Electron. We need to start two services: the web server and the Electron server.
pnpm run dev:client
After it starts successfully, we can proceed to start Electron.
pnpm run start-electron
pnpm run build:odc
The packaged artifacts can be found in dist/renderer
.
# Build for win, linux, mac
node ./scripts/client/build.js all
You can adjust the command parameters to selectively build different installation packages. Currently, the following types are supported:
- mac - dmg installation package
- linux_x86 - x86_64 version deb, AppImage installation package
- linux_aarch64 - arm64 version deb, AppImage installation package
- win - win32, win64 version installation package
- all - all installation packages