You can find documentation about the DTS system, including information on building the system, running the system, and the functionalities included in the system, by visiting the following links.
Please visit release section to get latest version of DTS.
We have created communication channels to provide support to our community. Please look there if you are looking for help regarding DTS system or any Dasharo related stuff.
Thank you for using Dasharo Tools Suite Community Edition. If you have encountered any problems with this version, or would like to provide feedback for us - please open an issue on dasharo-issues repository.
This section contains the technical aspects of the DTS release process. The
recipients of this information should be those authorised to issue DTS
releases.
Below are information on how to publish production and develop releases.
-
Productionreleases deploy images to GitHub Release pages andboot.3mdeb.com/boot.dasharo.compages to boot via iPXE. -
Developreleases deploy images to GitHub Release pages, so not all users will be able to use them via iPXE.
Please follow the steps below to release a new production DTS image.
-
Make sure that everything that should go into the given release is merged to
main. -
Bump the version in
meta-dts-distro/conf/distro/dts-distro.conffile.Note: In cases where MINOR or MAJOR part of version is updated, please inform one of the maintainers as there will be needed new keys to sign the binaries in next step of CI/CD pipeline.
-
Create and push tag that match the newly bumped version.
From here, rest of the jobs should be carried out by the GitHub and Gitea
Actions. Whole pipeline of creating DTS release consists of two steps.
-
First is done on GitHub Actions. Here we build the
DTSimage and push the binaries toboot.dasharo.com. -
Second is done on Gitea Actions. Here we push the ipxe menu to
boot.3mdeb.comand sign theDTSbinaries. The last step of Gitea Actions creates new release at thehttps://github.com/Dasharo/meta-dts/releasesfrom where binaries can be downloaded.
Please follow the steps below to release a new develop DTS image.
-
Make sure that everything that should go into the given release is merged to
main. -
Bump the version in
meta-dts-distro/conf/distro/dts-distro.conffile by adding-rcXsuffix.Note: X should increase every time new develop release is created.
-
Create and push tag that match the newly bumped version.
From here, rest of the jobs should be carried out by the GitHub and Gitea
Actions. Whole pipeline of creating DTS release consists of two steps.
-
First is done on GitHub Actions. Here we build the
DTSimage. -
Second is done on Gitea Actions. Here we sign the
DTSbinaries and creates new develop release at thehttps://github.com/Dasharo/meta-dts/releasesfrom where binaries can be downloaded.
By default the DTS uses https://3mdeb.com/open-source-firmware/Dasharo as a
source of downloaded artifacts in case of community releases. This behaviour can
be changed by starting dts script from the command line with
FW_STORE_URL_DEV variable set to the http address that is serving the update
files.
Below there is a list of steps that one need to do, to fetch binaries from local server.
-
On host PC create
dasharo-updatesdirectory and from it start the http python module, as a port you can use e.g.1234.mkdir dasharo-updates && cd dasharo-updates python -m http.server 1234
-
Inside
dasharo-updatesdirectory create the same folder structure as there is for your update files onhttps://3mdeb.com/open-source-firmware/Dasharo. E.g. forv1.7.2ofNovaCustom NS5X ADLyou need to create pathnovacustom_ns5x_adl/v1.7.2/and inside put binaries, hashes and signatures from that release. -
Boot
DTSand start shell by pressing9. -
Start
dtsscript withFW_STORE_URL_DEVvariable set to started server on the host PC. E.g. if the PC has IP address192.168.1.14use below command.FW_STORE_URL_DEV="http://192.168.1.14:1234" dts -
Normal
dtsmenu entry will be displayed but any request to the server with binaries will be done tohttp://192.168.1.14:1234instead ofhttps://3mdeb.com/open-source-firmware/Dasharo.