• 1 Post
  • 28 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2023

help-circle



  • ~53 W

    • Server:

      • AMD Ryzen 5 5600G
      • 4x16 GB DDR4 3200 Mhz
      • 256 GB NVMe as boot-disk
      • 2x256 GB Samsung SSDs for VMs
      • 2x2 TB WD Red Plus HDDs
    • Mini PC: Beelink S12 N95

      • 16 GB DDR4
      • 256 GB NVMe
    • 8 port unmanaged TP Link switch

    I would like to expand my storage, however I don’t have any available SATA ports and I believe adding an HBA would increase the idle draw about 8 W. I might just upgrade the SSDs and split the storage between the HDDs and SSDs.






  • I just did another test.

    You should be able to create the directories manually. I cheated by simply cloning the repo and copying them to the bind mount location like so. You can use the bind mount method like you wanted.

    git clone https://github.com/mdshack/shotshare
    cp -r shotshare/storage/* /srv/dev-disk-by-uuid-7fe66601-5ca0-4c09-bc13-a015025fe53a/Files/Shotshare/shotshare_data/
    chown 82:82 -R /srv/dev-disk-by-uuid-7fe66601-5ca0-4c09-bc13-a015025fe53a/Files/Shotshare/shotshare_data
    


  • This appears to be the exact same problem as https://github.com/mdshack/shotshare/issues/31

    For testing I just spun up a VM with Docker, I tried the same compose file as you. I found I had to use the volume instead of a bind mount for /app/storage.

    This compose file should work.

    version: "3.3"
    services:
      shotshare:
        ports:
          - 2000:80
        environment:
          - HOST=:80
          - ALLOW_REGISTRATION=false
        volumes:
          - shotshare_data:/app/storage
          - /srv/dev-disk-by-uuid-7fe66601-5ca0-4c09-bc13-a015025fe53a/Files/Shotshare/database.sqlite:/app/database/database.sqlite
          - /srv/dev-disk-by-uuid-7fe66601-5ca0-4c09-bc13-a015025fe53a/Files/Shotshare/.env:/app/.env
        restart: unless-stopped
        container_name: shotshare
        image: mdshack/shotshare:latest
    volumes:
        shotshare_data:
    networks: {}
    








  • Thanks for the reassurance. What I currently have is exactly that, RAID for the local data, and a spare drive that is mounted and unmount when data is backed up, and that is rsynced offsite to a cloud provider. I figured that my current setup was really reliable as I had slowly been researching and working on this over a few years.

    I have a sort of itch to play with a mini PC, I guess it would be best not to hurt any of my important data by downgrading the setup, however this is a good time to really sort and figure out what I need and is important and what isn’t as important and can be reobtained if something fails on the mini PC.