Based on the CI of the decky-plugin-database, this will be a dockerfile that demonstrates to developers how they would build a custom backend that would then be grabbed by decky-plugin-database during it's CI/CD process and bundle it with the plugin before sending it to the store.
Located within the directory backend will be a folder containing the source code for the relevant backend the developer wants to use.
Our dockerfile will look something like this
(we will not be using arch latest but libraries that match the Deck's current stable versions once ready)
FROM archlinux:latest
ADD ./backend/ /source
ADD ./build/backend /build
WORKDIR /source
# Build code goes here
Built binaries will end up in the build folder of the docker container, which will then be handled by the CD steps of decky-plugin-database
[x] Dockerfile has commands to demonstrate where source code should be placed.
This is for integration with the CI building of plugins in the plugin-database.
[ ] Dockerfile has commands to move built binaries to correct bin directory.
This is for integration with the CD of plugins to the plugin-store.
Based on the CI of the decky-plugin-database, this will be a dockerfile that demonstrates to developers how they would build a custom backend that would then be grabbed by decky-plugin-database during it's CI/CD process and bundle it with the plugin before sending it to the store.
Located within the directory
backendwill be a folder containing the source code for the relevant backend the developer wants to use.Our dockerfile will look something like this (we will not be using arch latest but libraries that match the Deck's current stable versions once ready)
Built binaries will end up in the build folder of the docker container, which will then be handled by the CD steps of decky-plugin-database