Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Apr 09 11:06
    gelato opened #186
  • Apr 09 01:45
    hkalexling unpinned #148
  • Apr 03 02:20
    toxinu labeled #185
  • Apr 03 02:20
    toxinu opened #185
  • Mar 30 04:49
    hkalexling closed #184
  • Mar 29 18:48
    zFerry98 labeled #184
  • Mar 29 18:48
    zFerry98 opened #184
  • Mar 29 17:59
    zFerry98 labeled #183
  • Mar 29 17:59
    zFerry98 opened #183
  • Mar 29 14:34
    zFerry98 edited #181
  • Mar 29 14:33
    zFerry98 edited #181
  • Mar 29 12:54
    zFerry98 edited #182
  • Mar 29 12:49
    zFerry98 opened #182
  • Mar 29 12:49
    zFerry98 labeled #182
  • Mar 29 12:23
    zFerry98 opened #181
  • Mar 29 00:42
    hkalexling synchronize #180
  • Mar 28 23:55
    hkalexling synchronize #180
  • Mar 28 14:25
    hkalexling edited #180
  • Mar 28 14:20
    hkalexling assigned #180
  • Mar 28 14:20
    hkalexling labeled #180
DeuceFFXI
@DeuceFFXI
I've been trying to rack my brain around why I can't write to my library folder. Using docker in unRaid. It's nested in a private share, which I do have access to. If I try to edit the info.json file it says root/TOWER has access, but none of my other users with access to the private share can write to it.
Alex Ling
@hkalexling
@DeuceFFXI Docker would always interact with your file system as the root user. The info.json file is created by the docker container, so it's owned by root, and you will need to sudo to edit it.
DeuceFFXI
@DeuceFFXI
and if I just wish to write to the library folder? same thing?
Alex Ling
@hkalexling
@DeuceFFXI If the folder was created by the docker container then yes you will need root access. If you created the folder and then mounted it to the container you should be to write to it.
If you don't want the container to act as root, you should start it with the --user argument
DeuceFFXI
@DeuceFFXI
yeah it was created by the container, I suppose it would be easier if I change the library path in the config.yml to a new folder I do have access to?
I'm new to unraid, so not too familiar with using CLI to make changes
Alex Ling
@hkalexling
@DeuceFFXI Changing the library path in the config file won't help. The path in the config file points to a folder in the container. What you need to do is to map a folder on your host system that you have access to to the container. For example, you can map /your/manga/library (on the host system) to /root/mango/library (in the container). And in the config file the library path would still be /root/mango/library, because Mango doesn't know it's running in a Docker container, and there's no /your/manga/library in the container.
DeuceFFXI
@DeuceFFXI
@hkalexling so this is my folder structure, /your/media/manga/library with mango.db, queue.db nested in the same place. So, I just want to make sure, Mango scans the library folder that it created for .zip .cbz etc? Or do I need to place those files elsewhere? In the container settings the config for "Mangas" was set to /your/media/manga/
Alex Ling
@hkalexling
@DeuceFFXI You need to map the host folder (/your/media/manga/library ) to your container. I don't use Unraid so not sure how you can do this with the GUI.
Alex Ling
@hkalexling
@DeuceFFXI Are you using this template https://github.com/selfhosters/unRAID-CA-templates/blob/master/templates/mango.xml? If so you should set "Mangas" to /your/media/manga/library, and keep the library path option in /mnt/user/appdata/Mango/config.yml unchanged (keep the default value /root/mango/library)
ברוך טסמה
@baruchtasma1:matrix.org
[m]
can you send me a tutorial how to get in the mango site?\
ksalaba
@ksalaba

@hkalexling My .env is
```#Port that exposes the HTTP frontend
PORT=2202

Path to the mango main director

This directory holds the database and the library files

MAIN_DIRECTORY_PATH=/mount/USB_External_12TB/storage/Mango/Data

Path to the mango config directory

This directory holds the mango configuration path

CONFIG_DIRECTORY_PATH=/mount/USB_External_12TB/storage/Mango/Config```

Maybe the problem is my lack of understanding on Copy the env.example file to .env
I have that config saved to a file called .env in the folder along with another file called mango.env with the same config. They exist with the repo files and where I am running docker-compose up from. /mount/USB_External_12TB/storage/Mango/Repo/Mango/

ksalaba
@ksalaba
@baruchtasma1:matrix.org Did you try localhost:9000 or whatever port you set from the instructions? ​https://getmango.app/#/Readme/?id=installation
Alex Ling
@hkalexling
@ksalaba Your .env file seems correct, but for some reason, it's not being used by Docker. Can you try to manually export the values in your shell (i.e., export PORT=2202, export MAIN_DIRECTORY_PATH=/your/path, export CONFIG_DIRECTORY_PATH=/your/path) and then do docker-compose up again?
The .env file is to set the default values for some environment variables, and the values in your shell would take precedence
or try docker-compose --env-file .env up. See https://docs.docker.com/compose/environment-variables/
ksalaba
@ksalaba

@hkalexling I got the configs to work, the issue was I had messed with docker-compose.yml file. I set it back to defaults and it correctly set environments. Looking at docker-compose.yml, arn't the .env tags and variables backwards? I.e. under volumes:

  • ${MAIN_DIRECTORY_PATH}:/root/mango be ` - MAIN_DIRECTORY_PATH:${MAIN_DIRECTORY_PATH}
    Where you're passing the .env tag to the environment variable?

If I am just using docker wrong, or if these are legitimate bugs. If the latter let me know, and I will submit them.

I figured out the rest of my issues. the :9000 of "${PORT}:9000" is the containers internal port. The port tag is setting the listening port for docker. After I figured that out, I was able to actually hit Mango's site! Hurray! Thank you Alex, and sorry for my bumbling

Does ${MAIN_DIRECTORY_PATH}:/root/mango mean for the container's internal path of /root/mango, you are mapping the external path of ${MAIN_DIRECTORY_PATH}?
Alex Ling
@hkalexling
@ksalaba Happy to know that you got it working :) Yes MAIN_DIRECTORY_PATH is the host path and /root/mango is the container path. If you are using Docker you don't need to change the paths and port in the mango config file because they are all internal.
it's easy to confuse the host paths with the container ones, so if you know how to improve the README feel free to submit a PR
ksalaba
@ksalaba
@hkalexling I am currently trying to figure out the library path. The Website says CURRENT LIBRARY PATH /root/mango/library Does that mean the docker path that I just mapped in .env, or /root/mango/library
ksalaba
@ksalaba
I have copied a few .cbr and .cbz files to both, but I cannot seem to see them
Alex Ling
@hkalexling
@ksalaba Just remember that Mango doesn’t know it’s running in a docker container, so everything Mango tells you is about the container. You should put your files in the directory you defined in the .env file.
The cbz/cbr files should be put in subdirectories in your library
Something like /path/to/mango/library/manga1/chapter1.cbz
ksalaba
@ksalaba

@hkalexling for compressed files should they all need to be put into subdirectories? I was using Ubooquity (but got fed up with it), and I had to format all my files from zip and rar to .cbz and cbr. Ubooquity could then load the data directly out of the .cbz and .cbr

Does mango do the same thing? Some of my zips are a zip within a zip. How does mango handle that?

For example Vinland Saga v17.cbz\Vinland Saga v17\Vinland Saga v17\17_193.jpg is the path inside the cbz I need to drill down to for the jpg
Alex Ling
@hkalexling
@ksalaba yes all archive files should be put into subdirectories. Mango doesn’t support nested zip files at this moment. If you want feel free to submit a feature request on GitHub and provide a usecase
ksalaba
@ksalaba
I am currently copying 1.5k zips/rars/cbz/cbr to my mongo/library location. I will need to create a subfolder for each before I see them? (well a lot of them are series, so not a big deal, but I am trying to ask that Mango requires a subfolder to exist before it can see the file)
Alex Ling
@hkalexling
@ksalaba no you don’t need a sub folder for each. You can put them all in a single sub folder. Please see the link above and read the README
ksalaba
@ksalaba
@hkalexling got it figured out! Everything is working great! Thank you soo much
ksalaba
@ksalaba

In testing I just noticed this message /root/mango/library/Watashi-tachi Kabe/Watashi-tachi Kabe v01.cbr Archive error: Pathname cannot be converted from UTF-16BE to current locale.

checking logs I got a bunch of similar messages 2021/03/16 21:01:54 | Unable to extract archive /root/mango/library/Watashi-tachi Kabe/Watashi-tachi ni wa Kabe ga Aru v04hhh.cbr. Ignoring it. Archive error: Pathname cannot be converted from UTF-16BE to current locale.

Is this a language issue on my pi?

the folder inside the cbr that its trying to open is named '[築島治] 私たちには壁がある。04'
ksalaba
@ksalaba
seems to happen whenever I have Japanese file names
Alex Ling
@hkalexling
@ksalaba That sounds like a locale problem. You can try setting the LC_ALL environment variable in the container and see if it helps.
You can do this by adding the environment section to your docker-compose.yml file like so
version: '3'

services:
  mango:
    container_name: mango
    build:
      context: .
      dockerfile: ./Dockerfile.arm32v7
    expose:
      - ${PORT}
    ports:
      - "${PORT}:9000"
    volumes:
      - ${MAIN_DIRECTORY_PATH}:/root/mango
      - ${CONFIG_DIRECTORY_PATH}:/root/.config/mango
    environment:
      - LC_ALL=C.UTF-8
Note that Mango can only read images directly in the archives. For example, if you have file.cbr/foo/bar.jpg, you won't be able to see bar.jpg in Mango.
Ansh Bhalala
@crazyaccess-wms
Emm
is anyone availabe to help me run this on a docker
i have some questions about the config.yml
Alex Ling
@hkalexling
@crazyaccess-wms It might be more effective if you could write down the questions and wait for someone to answer ;-)
Tunae
@Tunae
hello, when I try to run the binary I either get Permission denied(as root) or this: mango.service - Mango manga server Loaded: loaded (/etc/xdg/systemd/user/mango.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2021-03-25 00:01:10 UTC; 1min 12s ago Process: 52832 ExecStart=/usr/local/bin/mango (code=exited, status=203/EXEC) Main PID: 52832 (code=exited, status=203/EXEC)
just found hkalexling/Mango#18
Tunae
@Tunae
lear@main:~$ chmod -x mango lear@main:~$ ./mango bash: ./mango: Permission denied
Alex Ling
@hkalexling
@Tunae you probably want chmod +x.
Tunae
@Tunae
Thanks, I feel pretty stupid now...
Tunae
@Tunae
Is there any way I can disable read progress?
Alex Ling
@hkalexling
@Tunae No but you can always choose to start reading from the beginning. Is there a particular reason why you want to disable it?