#YACREADER LIBRARY SERVER MAC UPGRADE#
#YACREADER LIBRARY SERVER MAC CODE#
#YACREADER LIBRARY SERVER MAC WINDOWS#

This is usually the version I use and they should be fairly safe to use but there is always a chance something is broken, but it is the fastest way to get the new features. You can find the development builds in a separated repository. Let us know if you need any help with the building process.

#YACREADER LIBRARY SERVER MAC CODE#

Would you like to see a package for your distro? Become a YACReader packager!!! Building from sourcesĭidn't find a suitable package for your platform? You can download the latest tarball or clone the source code respository and build YACReader for your own platform.

deb packages for Debian, Ubuntu and derivates (like Mint)

#YACREADER LIBRARY SERVER MAC UPGRADE#

Note: Installation requires the current version of brew cask so if already installed, if brew-cask-0.35.0 already installed or higher we are good to go, if not: brew upgrade brew-cask Linux Official packages: Intel 64 only (works on M1), requires 10.14 or later. Brew cask support is supplied by the community and might not be up to date. You can get YACReader for MacOSX using the official package(recommended) or brew cast.

#YACREADER LIBRARY SERVER MAC WINDOWS#

YACReader 9.046 for Windows 32bit (with 7zip and rar5 support).YACReader 9.046 for Windows 64bit (with 7zip and rar5 support).These are the available Windows versions: Of course, to get back to the original point, better diagnostics and logging would help with this along the way when working to implement headless docker containers.All versions of YACReader & YACReaderLibrary If you're still interested after that, we can talk about including a docker image (or images) in the YACReaderLibrary CI process, and if the docker can or should be improved in any way. I'll report back once I'm able to get everything up on Docker Hub. I'm pretty close to launching it and am using a Github Workflow to build and publish both the images and the manifest, since it's a fairly complicated set up and more that Docker Hub builds can handle. I recommend to use YACReaderLibrary to manage and keep your collection. My image will likely be slower to start than some of the other YACReaderLibraryServer docker images I've seen since it relies on s6 rather than an entrypoint.sh or system.d and it's built on the Ubuntu LTS cloud image (rather than Alpine, for example), however, I've gotten each variant down in size to around ~130mb (compressed), which I feel fine about, and they seem to function fast enough for my needs at least. YACReader is an app for reading comics in your iOS devices, and that's its main purpose, you can store and keep a library perfectly organized in your device, the only limit is the space available in it, but YACReader is not intented for keeping your only bakcup of comics. Both are working well now, though I could use some help testing on arm systems. Once launched it will run YACReaderLibrary Server using s6-overlay with a non-root service user and a be a multi-arch (automatically pulled to match the end user's system - amd64, arm64, or amrhf), and will allow the user to choose the compression backend their container is built with, either unarr (the default/latest option) or the p7zip. I haven't been in touch with any of the other YACReaderLibraryServer Docker image maintainers (probably not a bad idea), but I've kind of 'gone down the rabbit hole', and spent the last two weeks completely redeveloping my own container which I'm close to launching. I agree that not blocking running as root is probably the best idea (for now) since some other YACReaderLibraryServer docker images are set up to run that way.

Yacreader library server mac