Skip to content
This repository has been archived by the owner on Dec 22, 2020. It is now read-only.

Commit

Permalink
adding dynamic readme
Browse files Browse the repository at this point in the history
  • Loading branch information
thelamer committed Feb 14, 2019
1 parent e567bb5 commit 562a3e2
Show file tree
Hide file tree
Showing 2 changed files with 184 additions and 162 deletions.
202 changes: 139 additions & 63 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,97 +1,173 @@
[linuxserverurl]: https://linuxserver.io
[forumurl]: https://forum.linuxserver.io
[ircurl]: https://www.linuxserver.io/irc/
[podcasturl]: https://www.linuxserver.io/podcast/
[appurl]: https://github.com/evilhero/mylar
[hub]: https://hub.docker.com/r/linuxserver/mylar/
[![linuxserver.io](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/linuxserver_medium.png)](https://linuxserver.io)

[![linuxserver.io](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/linuxserver_medium.png)][linuxserverurl]
The [LinuxServer.io](https://linuxserver.io) team brings you another container release featuring :-

The [LinuxServer.io][linuxserverurl] team brings you another container release featuring easy user mapping and community support. Find us for support at:
* [forum.linuxserver.io][forumurl]
* [IRC][ircurl] on freenode at `#linuxserver.io`
* [Podcast][podcasturl] covers everything to do with getting the most from your Linux Server plus a focus on all things Docker and containerisation!
* regular and timely application updates
* easy user mappings (PGID, PUID)
* custom base image with s6 overlay
* weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
* regular security updates

# linuxserver/mylar
[![](https://images.microbadger.com/badges/version/linuxserver/mylar.svg)](https://microbadger.com/images/linuxserver/mylar "Get your own version badge on microbadger.com")[![](https://images.microbadger.com/badges/image/linuxserver/mylar.svg)](https://microbadger.com/images/linuxserver/mylar "Get your own image badge on microbadger.com")[![Docker Pulls](https://img.shields.io/docker/pulls/linuxserver/mylar.svg)][hub][![Docker Stars](https://img.shields.io/docker/stars/linuxserver/mylar.svg)][hub][![Build Status](https://ci.linuxserver.io/buildStatus/icon?job=Docker-Builders/x86-64/x86-64-mylar)](https://ci.linuxserver.io/job/Docker-Builders/job/x86-64/job/x86-64-mylar/)
Find us at:
* [Discord](https://discord.gg/YWrKVTn) - realtime support / chat with the community and the team.
* [IRC](https://irc.linuxserver.io) - on freenode at `#linuxserver.io`. Our primary support channel is Discord.
* [Blog](https://blog.linuxserver.io) - all the things you can do with our containers including How-To guides, opinions and much more!
* [Podcast](https://anchor.fm/linuxserverio) - on hiatus. Coming back soon (late 2018).

An automated Comic Book downloader (cbr/cbz) for use with SABnzbd, NZBGet and torrents. [mylar](https://github.com/evilhero/mylar)
# PSA: Changes are happening

From August 2018 onwards, Linuxserver are in the midst of switching to a new CI platform which will enable us to build and release multiple architectures under a single repo. To this end, existing images for `arm64` and `armhf` builds are being deprecated. They are replaced by a manifest file in each container which automatically pulls the correct image for your architecture. You'll also be able to pull based on a specific architecture tag.

TLDR: Multi-arch support is changing from multiple repos to one repo per container image.

# [linuxserver/mylar](https://github.com/linuxserver/docker-mylar)
[![](https://img.shields.io/discord/354974912613449730.svg?logo=discord&label=LSIO%20Discord&style=flat-square)](https://discord.gg/YWrKVTn)
[![](https://images.microbadger.com/badges/version/linuxserver/mylar.svg)](https://microbadger.com/images/linuxserver/mylar "Get your own version badge on microbadger.com")
[![](https://images.microbadger.com/badges/image/linuxserver/mylar.svg)](https://microbadger.com/images/linuxserver/mylar "Get your own version badge on microbadger.com")
![Docker Pulls](https://img.shields.io/docker/pulls/linuxserver/mylar.svg)
![Docker Stars](https://img.shields.io/docker/stars/linuxserver/mylar.svg)
[![Build Status](https://ci.linuxserver.io/buildStatus/icon?job=Docker-Pipeline-Builders/docker-mylar/master)](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-mylar/job/master/)
[![](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/mylar/latest/badge.svg)](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/mylar/latest/index.html)

[Mylar](https://github.com/evilhero/mylar) is an automated Comic Book downloader (cbr/cbz) for use with SABnzbd, NZBGet and torrents.

[![mylar](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/mylar-icon.png)](https://github.com/evilhero/mylar)

## Supported Architectures

Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list).

Simply pulling `linuxserver/mylar` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v6-latest |

[![mylar](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/mylar-icon.png)][appurl]

## Usage

Here are some example snippets to help you get started creating a container.

### docker

```
docker create \
--name=mylar \
-v <path to data>:/config \
-v <downloads-folder>:/downloads \
-v <comics-folder>:/comics \
-e PGID=<gid> -e PUID=<uid> \
-e TZ=<timezone> \
-p 8090:8090 \
linuxserver/mylar
--name=mylar \
-e PUID=1001 \
-e PGID=1001 \
-p 8090:8090 \
-v <path to data>:/config \
-v <comics-folder>:/comics \
-v <downloads-folder>:/downloads \
--restart unless-stopped \
linuxserver/mylar
```

## Parameters

`The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side.
For example with a port -p external:internal - what this shows is the port mapping from internal to external of the container.
So -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080
http://192.168.x.x:8080 would show you what's running INSIDE the container on port 80.`
### docker-compose

Compatible with docker-compose v2 schemas.

```
---
version: "2"
services:
mylar:
image: linuxserver/mylar
container_name: mylar
environment:
- PUID=1001
- PGID=1001
volumes:
- <path to data>:/config
- <comics-folder>:/comics
- <downloads-folder>:/downloads
ports:
- 8090:8090
mem_limit: 4096m
restart: unless-stopped
```

* `-p 8090` - the port(s)
* `-v /config` - where mylar should store config files
* `-v /downloads` - map to your downloads folder
* `-v /comics` - map to your comics folder
* `-e PGID` for GroupID - see below for explanation
* `-e PUID` for UserID - see below for explanation
* `-e TZ` for setting timezone information, eg Europe/London
## Parameters

It is based on alpine linux with s6 overlay, for shell access whilst the container is running do `docker exec -it mylar /bin/bash`.
Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.

### User / Group Identifiers
| Parameter | Function |
| :----: | --- |
| `-p 8090` | WebUI |
| `-e PUID=1001` | for UserID - see below for explanation |
| `-e PGID=1001` | for GroupID - see below for explanation |
| `-v /config` | Where mylar should store config files. |
| `-v /comics` | Map to your comics folder. |
| `-v /downloads` | Map to your downloads folder. |

Sometimes when using data volumes (`-v` flags) permissions issues can arise between the host OS and the container. We avoid this issue by allowing you to specify the user `PUID` and group `PGID`. Ensure the data volume directory on the host is owned by the same user you specify and it will "just work" ™.
## User / Group Identifiers

In this instance `PUID=1001` and `PGID=1001`. To find yours use `id user` as below:
When using volumes (`-v` flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance `PUID=1001` and `PGID=1001`, to find yours use `id user` as below:

```
$ id <dockeruser>
$ id username
uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)
```

## Setting up the application

The web ui for settings etc, is on `<your-ip>:8090`
For more detailed setup refer [mylar](https://github.com/evilhero/mylar).
&nbsp;
## Application Setup

## Info
The web ui for settings etc, is on `<your-ip>:8090`
For more detailed setup refer [Mylar](https://github.com/evilhero/mylar).

* To monitor the logs of the container in realtime `docker logs -f mylar`.

* container version number

`docker inspect -f '{{ index .Config.Labels "build_version" }}' mylar`
## Support Info

* Shell access whilst the container is running: `docker exec -it mylar /bin/bash`
* To monitor the logs of the container in realtime: `docker logs -f mylar`
* container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' mylar`
* image version number

`docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/mylar`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/mylar`

## Updating Info

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the [Application Setup](#application-setup) section above to see if it is recommended for the image.

Below are the instructions for updating containers:

### Via Docker Run/Create
* Update the image: `docker pull linuxserver/mylar`
* Stop the running container: `docker stop mylar`
* Delete the container: `docker rm mylar`
* Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your `/config` folder and settings will be preserved)
* Start the new container: `docker start mylar`
* You can also remove the old dangling images: `docker image prune`

### Via Docker Compose
* Update the image: `docker-compose pull linuxserver/mylar`
* Let compose update containers as necessary: `docker-compose up -d`
* You can also remove the old dangling images: `docker image prune`

## Versions

+ **17.08.18:** Rebase to alpine 3.8.
+ **06.07.18:** Add `html5lib` python package
+ **14.06.18:** Add `requests` python package
+ **12.12.17:** Rebase to alpine 3.7.
+ **21.07.17:** Internal git pull instead of at runtime.
+ **25.05.17:** Rebase to alpine 3.6.
+ **19.02.17:** Use quiet option for cleaner console log,
app logs to file anyways.
+ **07.02.17:** Rebase to alpine 3.5.
+ **14.10.16:** Add version layer information.
+ **10.09.16:** Add layer badges to README.
+ **28.08.16:** Add badges to README.
+ **08.08.16:** Rebase to alpine linux.
+ **26.01.16:** Initial Release.
* **11.02.19:** - Pipeline logic and multi arch.
* **17.08.18:** - Rebase to alpine 3.8.
* **06.07.18:** - Add `html5lib` python package.
* **14.06.18:** - Add `requests` python package.
* **12.12.17:** - Rebase to alpine 3.7.
* **21.07.17:** - Internal git pull instead of at runtime.
* **25.05.17:** - Rebase to alpine 3.6.
* **19.02.17:** - Use quiet option for cleaner console log, app logs to file anyways.
* **07.02.17:** - Rebase to alpine 3.5.
* **14.10.16:** - Add version layer information.
* **10.09.16:** - Add layer badges to README.
* **28.08.16:** - Add badges to README.
* **08.08.16:** - Rebase to alpine linux.
* **26.01.16:** - Initial release.
144 changes: 45 additions & 99 deletions readme-vars.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,103 +2,49 @@

# project information
project_name: mylar
full_custom_readme: |
{% raw -%}
[linuxserverurl]: https://linuxserver.io
[forumurl]: https://forum.linuxserver.io
[ircurl]: https://www.linuxserver.io/irc/
[podcasturl]: https://www.linuxserver.io/podcast/
[appurl]: https://github.com/evilhero/mylar
[hub]: https://hub.docker.com/r/linuxserver/mylar/
[![linuxserver.io](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/linuxserver_medium.png)][linuxserverurl]
The [LinuxServer.io][linuxserverurl] team brings you another container release featuring easy user mapping and community support. Find us for support at:
* [forum.linuxserver.io][forumurl]
* [IRC][ircurl] on freenode at `#linuxserver.io`
* [Podcast][podcasturl] covers everything to do with getting the most from your Linux Server plus a focus on all things Docker and containerisation!
# linuxserver/mylar
[![](https://images.microbadger.com/badges/version/linuxserver/mylar.svg)](https://microbadger.com/images/linuxserver/mylar "Get your own version badge on microbadger.com")[![](https://images.microbadger.com/badges/image/linuxserver/mylar.svg)](https://microbadger.com/images/linuxserver/mylar "Get your own image badge on microbadger.com")[![Docker Pulls](https://img.shields.io/docker/pulls/linuxserver/mylar.svg)][hub][![Docker Stars](https://img.shields.io/docker/stars/linuxserver/mylar.svg)][hub][![Build Status](https://ci.linuxserver.io/buildStatus/icon?job=Docker-Builders/x86-64/x86-64-mylar)](https://ci.linuxserver.io/job/Docker-Builders/job/x86-64/job/x86-64-mylar/)
An automated Comic Book downloader (cbr/cbz) for use with SABnzbd, NZBGet and torrents. [mylar](https://github.com/evilhero/mylar)
[![mylar](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/mylar-icon.png)][appurl]
## Usage
```
docker create \
--name=mylar \
-v <path to data>:/config \
-v <downloads-folder>:/downloads \
-v <comics-folder>:/comics \
-e PGID=<gid> -e PUID=<uid> \
-e TZ=<timezone> \
-p 8090:8090 \
linuxserver/mylar
```
## Parameters
`The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side.
For example with a port -p external:internal - what this shows is the port mapping from internal to external of the container.
So -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080
http://192.168.x.x:8080 would show you what's running INSIDE the container on port 80.`
* `-p 8090` - the port(s)
* `-v /config` - where mylar should store config files
* `-v /downloads` - map to your downloads folder
* `-v /comics` - map to your comics folder
* `-e PGID` for GroupID - see below for explanation
* `-e PUID` for UserID - see below for explanation
* `-e TZ` for setting timezone information, eg Europe/London
It is based on alpine linux with s6 overlay, for shell access whilst the container is running do `docker exec -it mylar /bin/bash`.
### User / Group Identifiers
Sometimes when using data volumes (`-v` flags) permissions issues can arise between the host OS and the container. We avoid this issue by allowing you to specify the user `PUID` and group `PGID`. Ensure the data volume directory on the host is owned by the same user you specify and it will "just work" ™.
In this instance `PUID=1001` and `PGID=1001`. To find yours use `id user` as below:
```
$ id <dockeruser>
uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)
```
## Setting up the application
project_url: "https://github.com/evilhero/mylar"
project_logo: "https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/mylar-icon.png"
project_blurb: "[{{ project_name|capitalize }}]({{ project_url }}) is an automated Comic Book downloader (cbr/cbz) for use with SABnzbd, NZBGet and torrents."
project_lsio_github_repo_url: "https://github.com/linuxserver/docker-{{ project_name }}"

# supported architectures
available_architectures:
- { arch: "{{ arch_x86_64 }}", tag: "amd64-latest"}
- { arch: "{{ arch_arm64 }}", tag: "arm64v8-latest"}
- { arch: "{{ arch_armhf }}", tag: "arm32v6-latest"}

# container parameters
param_container_name: "{{ project_name }}"
param_usage_include_vols: true
param_volumes:
- { vol_path: "/config", vol_host_path: "<path to data>", desc: "Where mylar should store config files." }
- { vol_path: "/comics", vol_host_path: "<comics-folder>", desc: "Map to your comics folder." }
- { vol_path: "/downloads", vol_host_path: "<downloads-folder>", desc: "Map to your downloads folder." }
param_usage_include_env: false

param_usage_include_ports: true
param_ports:
- { external_port: "8090", internal_port: "8090", port_desc: "WebUI" }

# application setup block
app_setup_block_enabled: true
app_setup_block: |
The web ui for settings etc, is on `<your-ip>:8090`
For more detailed setup refer [mylar](https://github.com/evilhero/mylar).
## Info
* To monitor the logs of the container in realtime `docker logs -f mylar`.
* container version number
`docker inspect -f '{{ index .Config.Labels "build_version" }}' mylar`
* image version number
`docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/mylar`
## Versions
+ **17.08.18:** Rebase to alpine 3.8.
+ **06.07.18:** Add `html5lib` python package
+ **14.06.18:** Add `requests` python package
+ **12.12.17:** Rebase to alpine 3.7.
+ **21.07.17:** Internal git pull instead of at runtime.
+ **25.05.17:** Rebase to alpine 3.6.
+ **19.02.17:** Use quiet option for cleaner console log,
app logs to file anyways.
+ **07.02.17:** Rebase to alpine 3.5.
+ **14.10.16:** Add version layer information.
+ **10.09.16:** Add layer badges to README.
+ **28.08.16:** Add badges to README.
+ **08.08.16:** Rebase to alpine linux.
+ **26.01.16:** Initial Release.
{%- endraw %}
For more detailed setup refer [{{ project_name|capitalize }}]({{ project_url }}).
# changelog
changelogs:
- { date: "11.02.19:", desc: "Pipeline logic and multi arch."}
- { date: "17.08.18:", desc: "Rebase to alpine 3.8."}
- { date: "06.07.18:", desc: "Add `html5lib` python package."}
- { date: "14.06.18:", desc: "Add `requests` python package."}
- { date: "12.12.17:", desc: "Rebase to alpine 3.7."}
- { date: "21.07.17:", desc: "Internal git pull instead of at runtime."}
- { date: "25.05.17:", desc: "Rebase to alpine 3.6."}
- { date: "19.02.17:", desc: "Use quiet option for cleaner console log, app logs to file anyways."}
- { date: "07.02.17:", desc: "Rebase to alpine 3.5."}
- { date: "14.10.16:", desc: "Add version layer information."}
- { date: "10.09.16:", desc: "Add layer badges to README."}
- { date: "28.08.16:", desc: "Add badges to README."}
- { date: "08.08.16:", desc: "Rebase to alpine linux."}
- { date: "26.01.16:", desc: "Initial release."}

0 comments on commit 562a3e2

Please sign in to comment.