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
* While contributing make sure to make all your changes before creating a Pull Request, as our pipeline builds each commit after the PR is open.
6
+
* Read, and fill the Pull Request template
7
+
* If this is a fix for a typo in code or documentation in the README please file an issue
8
+
* If the PR is addressing an existing issue include, closes #\<issue number>, in the body of the PR commit message
9
+
* If you want to discuss changes, you can also bring it up in [#dev-talk](https://discordapp.com/channels/354974912613449730/757585807061155840) in our [Discord server](https://discord.gg/YWrKVTn)
10
+
11
+
## Common files
12
+
13
+
| File | Use case |
14
+
| :----: | --- |
15
+
|`Dockerfile`| Dockerfile used to build amd64 images |
16
+
|`Dockerfile.aarch64`| Dockerfile used to build 64bit ARM architectures |
17
+
|`Dockerfile.armhf`| Dockerfile used to build 32bit ARM architectures |
18
+
|`Jenkinsfile`| This file is a product of our builder and should not be edited directly. This is used to build the image |
19
+
|`jenkins-vars.yml`| This file is used to generate the `Jenkinsfile` mentioned above, it only affects the build-process |
20
+
|`package_versions.txt`| This file is generated as a part of the build-process and should not be edited directly. It lists all the installed packages and their versions |
21
+
|`README.md`| This file is a product of our builder and should not be edited directly. This displays the readme for the repository and image registries |
22
+
|`readme-vars.yml`| This file is used to generate the `README.md`|
23
+
24
+
## Readme
25
+
26
+
If you would like to change our readme, please __**do not**__ directly edit the readme, as it is auto-generated on each commit.
27
+
Instead edit the [readme-vars.yml](https://github.com/linuxserver/docker-swag/edit/master/readme-vars.yml).
28
+
29
+
These variables are used in a template for our [Jenkins Builder](https://github.com/linuxserver/docker-jenkins-builder) as part of an ansible play.
30
+
Most of these variables are also carried over to [docs.linuxserver.io](https://docs.linuxserver.io/images/docker-swag)
31
+
32
+
### Fixing typos or clarify the text in the readme
33
+
34
+
There are variables for multiple parts of the readme, the most common ones are:
35
+
36
+
| Variable | Description |
37
+
| :----: | --- |
38
+
|`project_blurb`| This is the short excerpt shown above the project logo. |
39
+
|`app_setup_block`| This is the text that shows up under "Application Setup" if enabled |
40
+
41
+
### Parameters
42
+
43
+
The compose and run examples are also generated from these variables.
44
+
45
+
We have a [reference file](https://github.com/linuxserver/docker-jenkins-builder/blob/master/vars/_container-vars-blank) in our Jenkins Builder.
46
+
47
+
These are prefixed with `param_` for required parameters, or `opt_param` for optional parameters, except for `cap_add`.
48
+
Remember to enable param, if currently disabled. This differs between parameters, and can be seen in the reference file.
49
+
50
+
Devices, environment variables, ports and volumes expects its variables in a certain way.
After you make any changes to the templates, you can use our [Jenkins Builder](https://github.com/linuxserver/docker-jenkins-builder) to have the files updated from the modified templates. Please use the command found under `Running Locally` [on this page](https://github.com/linuxserver/docker-jenkins-builder/blob/master/README.md) to generate them prior to submitting a PR.
91
+
92
+
## Dockerfiles
93
+
94
+
We use multiple Dockerfiles in our repos, this is because sometimes some CPU architectures needs different packages to work.
95
+
If you are proposing additional packages to be added, ensure that you added the packages to all the Dockerfiles in alphabetical order.
The ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static`
109
+
```
110
+
docker run --rm --privileged multiarch/qemu-user-static:register --reset
111
+
```
112
+
113
+
Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64`.
114
+
115
+
## Update the chagelog
116
+
117
+
If you are modifying the Dockerfiles or any of the startup scripts in [root](https://github.com/linuxserver/docker-swag/tree/master/root), add an entry to the changelog
118
+
119
+
```yml
120
+
changelogs:
121
+
- { date: "DD.MM.YY:", desc: "Added some love to templates" }
If you are new to Docker or this application our issue tracker is **ONLY** used for reporting bugs or requesting features. Please use [our discord server](https://discord.gg/YWrKVTn) for general support.
4
+
<!--- If you are new to Docker or this application our issue tracker is **ONLY** used for reporting bugs or requesting features. Please use [our discord server](https://discord.gg/YWrKVTn) for general support. --->
5
+
6
+
<!--- If this acts as a feature request please ask yourself if this modification is something the whole userbase will benefit from --->
7
+
<!--- If this is a specific change for corner case functionality or plugins please look at making a Docker Mod or local script https://blog.linuxserver.io/2019/09/14/customizing-our-containers/ -->
5
8
6
9
<!--- Provide a general summary of the issue in the Title above -->
7
10
@@ -22,9 +25,10 @@ If you are new to Docker or this application our issue tracker is **ONLY** used
22
25
4.
23
26
24
27
## Environment
25
-
**OS:**
26
-
**CPU architecture:** x86_64/arm32/arm64
27
-
**How docker service was installed:**
28
+
**OS:**
29
+
**CPU architecture:** x86_64/arm32/arm64
30
+
**How docker service was installed:**
31
+
<!--- ie. from the official docker repo, from the distro repo, nas OS provided, etc. -->
28
32
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
29
33
30
34
## Command used to create docker container (run/create/compose/screenshot)
<!--- Before submitting a pull request please check the following -->
8
8
9
-
<!--- If this is a fix for a typo in code or documentation in the README please file an issue and let us sort it out we do not need a PR -->
9
+
<!--- If this is a fix for a typo in code or documentation in the README please file an issue and let us sort it out we do not need a PR -->
10
10
<!--- Ask yourself if this modification is something the whole userbase will benefit from, if this is a specific change for corner case functionality or plugins please look at making a Docker Mod or local script https://blog.linuxserver.io/2019/09/14/customizing-our-containers/ -->
11
11
<!--- That if the PR is addressing an existing issue include, closes #<issue number> , in the body of the PR commit message -->
12
12
<!--- You have included links to any files / patches etc your PR may be using in the body of the PR commit message -->
@@ -21,7 +21,11 @@
21
21
22
22
------------------------------
23
23
24
-
We welcome all PR’s though this doesn’t guarantee it will be accepted.
24
+
-[ ] I have read the [contributing](https://github.com/linuxserver/docker-swag/blob/master/.github/CONTRIBUTING.md) guideline and understand that I have made the correct modifications
25
+
26
+
------------------------------
27
+
28
+
<!--- We welcome all PR’s though this doesn’t guarantee it will be accepted. -->
Copy file name to clipboardExpand all lines: .github/workflows/greetings.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,6 @@ jobs:
8
8
steps:
9
9
- uses: actions/first-interaction@v1
10
10
with:
11
-
issue-message: 'Thanks for opening your first issue here! Be sure to follow the [issue template](https://github.com/linuxserver/docker-swag/.github/ISSUE_TEMPLATE.md)!'
12
-
pr-message: 'Thanks for opening this pull request! Be sure to follow the [pull request template](https://github.com/linuxserver/docker-swag/.github/PULL_REQUEST_TEMPLATE.md)!'
11
+
issue-message: 'Thanks for opening your first issue here! Be sure to follow the [issue template](https://github.com/linuxserver/docker-swag/blob/master/.github/ISSUE_TEMPLATE.md)!'
12
+
pr-message: 'Thanks for opening this pull request! Be sure to follow the [pull request template](https://github.com/linuxserver/docker-swag/blob/master/.github/PULL_REQUEST_TEMPLATE.md)!'
0 commit comments