You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here we specify the filename for the docker compose file, the file that contains all the details required to
35
36
build the docker container(s).
@@ -39,20 +40,13 @@ The artifact will not work on any other device but what is specified.
39
40
A signing-key can also be specified if required, this will ensure that the artifact has not been changed after creation.
40
41
It will also force the artifact to only work on the mender server that contains the corresponding private key.
41
42
42
-
GitHub's upload-artifact action can then be used to upload the created artifact to GitHub.
43
-
Support for variables within the docker compose file is supported. See [here](https://docs.docker.com/compose/environment-variables/) for how to use compose file variables.
44
-
The variables can be passed in using the "compose-file-variables" input key. The format is "NAME=VARIABLE", multiple variables are separated by a space.
45
-
46
-
GitHub's upload-artifact action can be used to upload the created artifact to GitHub.
47
-
48
-
49
-
## Where does the upload go?
50
-
At the bottom of the workflow summary page, there is a dedicated section for artifacts.
43
+
We can then our other action that can upload the mender artifact to a mender server.
44
+
See [upload-artifact](https://github.com/actions/upload-artifact)
51
45
52
46
53
47
# Notes
54
48
For the artifact to work on mender, all mender devices need to have docker compose installed.
55
-
The docker-compose update module from this repo also needs to be placed in the
49
+
The `docker-compose` update module from this repo also needs to be placed in the
56
50
`/usr/share/mender/modules/v3`directory on all your mender devices.
0 commit comments