Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)SI
Posts
4
Comments
22
Joined
1 yr. ago

  • Not mine (I'm not at home right now) but here a pic of someone elses: https://imgur.com/JUTggFt as for why I need it... I don't really, but I like it and want it. I also don't need a 75% but would like one. That is what's cool about custom anything, right?

  • Mechanical Keyboards @lemmy.ml

    KBD75 like keyboard?

    Privacy @lemmy.ml

    What do you use as your personal domain for email?

  • Then you should be able to do like I said and it might solve whatever is happening. I also have both homepage and paperless in the same docker-compose file. If you set the container name for each container then you can just reference that in homepage widgets. For example here is my homepage and paperless:

     
        
    homepage:
        image: ghcr.io/gethomepage/homepage:latest
        container_name: homepage
        restart: unless-stopped
        environment:
          - PUID=1000
          - PGID=1000
          - TZ=Europe/Berlin
        volumes:
          - /opt/docker/homepage:/app/config
          - /var/run/docker.sock:/var/run/docker.sock:ro # (optional) For docker integrations)
    
      paperless:
        image: ghcr.io/paperless-ngx/paperless-ngx:latest
        container_name: paperless
        restart: unless-stopped
        depends_on:
          - paperless-redis
          - postgres
        networks:
          - proxy
        user: "1000"
        environment:
          - USERMAP_UID=1000
          - USERMAP_GID=1000
          - TZ=Europe/Berlin
          - PAPERLESS_REDIS=redis://paperless-redis:6379
          - PAPERLESS_TIKA_ENABLED=1
          - PAPERLESS_TIKA_GOTENBERG_ENDPOINT=http://gotenberg:3000/
          - PAPERLESS_TIKA_ENDPOINT=http://tika:9998/
          - PAPERLESS_DBENGINE=postgresql
          - PAPERLESS_DBHOST=postgres
          - PAPERLESS_DBNAME=paperless
          - PAPERLESS_DBUSER=paperless
          - PAPERLESS_DBPASS=password
        volumes:
          - /opt/docker/paperless/data:/usr/src/paperless/data
          - /opt/docker/paperless/export:/usr/src/paperless/export
          - /opt/docker/paperless/consume:/usr/src/paperless/consume
          - /mnt/paperless:/usr/src/paperless/media
    
    
      

    so both have conatiner_name set to the same string as the service name. And in my homepage widgets I just use the container name in the URL, example:

     
        
        - Paperless:
            icon: paperless-ngx
            href: https://paperless.local.tld/
            widget:
                type: paperlessngx
                url: http://paperless:8000/
                username: username
                password: password
    
    
      

    This only works if they are in the same docker network. If you don't explicitly set the network for the containers and they are in the same compose file then they should be in the same network.

  • Where is paperless in relation to homepage? For me i have both of them in the same docker host and same docker network on that host and with that i only need to set the paperless container name in the widget. If paperless is on another machine make sure there is no firewall blocking the port number.

  • Set up paperless-ngx and cannot get my scanner to send a scan to a FTP server. It supposedly supports sending to FTP but doesn't have much documentation for it. I've tried FTPS, SFTP, and unsecured FTP. Both secure types just cause it to error out. But with unsecured the scanner just freezes then reboots. Really annoying me. I'm about to give up and just scan to s USB thumb drive then copy the scans to the server.

  • I came here to basically say this. It's especially bad when you aren't even sure if you want to keep the service and are just testing it out. If I already have to go through a huge setup/troubleshooting process just to test the app, then I'm not feeling very good about it.

  • Oh I see. When I read your first comment I understood 'functional' to mean more like "it works but not very well". I did see in the github issues that they are working on SSO and Android Auto so when that comes I'll give it a try.

  • Correct. If I remove the save then the ROM will take me to the tutorial and everything. I hadn't done an md5 check but your first question had me try something else: i removed the save, started a new game on my phone and saved it the first moment I could. Closed retroarch and restarted it on my phone again, and I got the error again, even though the sage was created by that exact retroarch instance. Then i tried the mew save on the deck and it loaded fine. Seems like I just have an issue with retro arch on my other devices but not the save itself.

  • Steam Deck @sopuli.xyz

    Trying to run my EmuDeck RetroArch saves on other devices, getting an error.

    Selfhosted @lemmy.world

    Why Prometheus + Grafana over other monitoring options?