Pingvin: store data on a NAS?

[Stooovie]

Hi, I'd like to have Pingvin use my NAS to store the data. I see in the documentation I need to adjust the config.yaml to do that (adding DATA_DIRECTORY there), but it doesn't work. Data still store at /opt/pingvin-share/backend/data.

I also tried to adjust the docker compose yml like this, but that didn't work either as the install is apparently not using Docker:

services:
  pingvin-share:
    image: stonith404/pingvin-share # or ghcr.io/stonith404/pingvin-share
    restart: unless-stopped
    ports:
      - 3000:3000
    environment:
      - TRUST_PROXY=false # Set to true if a reverse proxy is in front
    volumes:
      - "/media/Public/pingvin:/opt/app/backend/data"
      - "/media/Public/pingvin/images:/opt/app/frontend/public/img"
    #      - "./config.yaml:/opt/app/config.yaml" # Add this line, if needed

My NAS folder is mounted via fstab at /media/Public/pingvin

Any more tips? Thanks!

[tremor021]

We are not their support. Ask this in their github.

[warmbo]

I agree, the documentation for this needs to be updated at least a little so we know what type of installation this was. As is none of their documented information on their website docs reflects how we can change it on an unknown install type.

[tremor021]

Couple of things here.

1. Its not a unknown install type. Its literaly by the dev instructions here: https://stonith404.github.io/pingvin-share/setup/installation. You wouldn't know it, because you don't read docs or the source code of the script you're about to install on your machine.
2. Why would we provide documentation on the stuff that should be clearly known by a person installing the app (linux, how shares work, mounting). We DO provide infos on details that are script specific, but general usage of the application is assumed to be known.
3. I'm not really sure when did people started thinking we are the ones who provide everything on a silver platter and to be a support for their not knowing of things they're dealing with, but seriously.... Minimum effort is assumed from your side and you are not able to provide even that (reading docs, source, undestanding how stuff works)
4. @Stooovie tried editing a docker compose file while it has nothing to do with docker.

Environment variable controls where data is stored. If you would read the docs, you would see it defaults to current directory/data, which is /opt/pingvin-share/backend/data. The app is doing what its supposed to do.
Set the variable correctly, and it will work the way you want. Once again, this has nothing to do with the install script, type of installation, God, MotoGP, etc etc This is basic linux usage

[MickLesk]

As a completion:

This is a community-led project. We provide the base installation and every USER can feel free to create a guide for their use case. We have almost no guides because everyone wants to have everything served directly or open up issues for extensions. Then feel free to write a proper guide for everyone.

[warmbo]

1. You wouldn't know it, because you don't read docs or the source code of the script you're about to install on your machine.

I did read the docs. That's how I know that their documentation is poorly worded and confusing at best.

2. Why would we provide documentation on the stuff that should be clearly known by a person installing the app

It should be clearly known, I agree, but in this case it was not able to be without at least hinting.

3. I'm not really sure when did people started thinking we are the ones who provide everything on a silver platter and to be a support for their not knowing of things they're dealing with, but seriously.... Minimum effort is assumed from your side and you are not able to provide even that (reading docs, source, undestanding how stuff works)

Now you're just being rude. Thank you for your minimum effort of adding a line of text to the webpage after the lengthy effort of your reply here.

[Stooovie]

Thanks. To complete even further:

1. I DID read the documentation, as clearly stated in the OP.
2. I DID adjust the environment variable as suggested (again, stated in OP), but it was ignored by Pingvin
3. I asked because I'm not a developer, so reading through the source or scripts only takes me so far. I was asking because the Proxmox scripts can and often do use non-default locations

[tremor021]

No, you said "I need to adjust the config.yaml to do that (adding DATA_DIRECTORY there), but it doesn't work."

Environment variables don't go in yaml file, as stated by the docs: For installation specific configuration, you can use environment variables.

so points 1, 2 you didn't do correctly. point 3 is understandable, not everyone is a dev, but understanding code and docs is kind of a prerequisite to use custom scripts.

To cut to the chase:
DATA_DIRECTORY=/opt/pingvindata pm2 restart all --update-env this is a quick shortcut to define and update env variable for a app using pm2. Adjust the path to your desire

[tremor021]

I'm going to add this as info on webpage, so we don't get these kind of issues again.

[Stooovie]

Great, thanks!

[warmbo]

The wording on their docs makes no mention of pm2 (sans a couple lines in the initial installation process we don't see when we use these scripts), so to know that it was supposed to be pm2 env vars being changed would've been quite a bit of work. I even stumbled into their Discord and they didn't seem to understand what was being asked. So thanks @tremor021 for somehow inherently understanding the program enough to be able to help everyone else.