

Anyone remember that video of a guy proving he can cook chicken by slapping it many times?
Anyone remember that video of a guy proving he can cook chicken by slapping it many times?
I need to use the IP for specific reasons concerning my setup; and I don’t want the two containers to share a Docker network.
This used to work exactly as is when I set it up, but doesn’t anymore.
I tinkered with it some more now and I found that while I can ping the docker host, I can’t actually wget anything from any docker services from within the Homepage container. Currently at a loss why that might be.
Would love to see it.
Here’s mine from the Paperless compose.yml (non functional):
webserver:
image: ghcr.io/paperless-ngx/paperless-ngx
[...]
labels:
- homepage.group=Productivity
- homepage.name=Paperless
- homepage.icon=paperless.png
- homepage.href=https://[LOCAL URL]
- homepage.description=Document Management
- homepage.widget.type=paperlessngx
- homepage.widget.url=http://[PAPERLESS IP:PORT]
- homepage.widget.key=[PAPERLESS API TOKEN]
And here’s the error from Homepage frontend:
API Error: Unknown error
URL: http://[PAPERLESS IP:PORT]/api/statistics/?format=json
Raw Error:
{
"errno": -110,
"code": "ETIMEDOUT",
"syscall": "connect",
"address": "[PAPERLESS IP]",
"port": [PAPERLESS PORT]
}
I don’t think it’s you. The paperless widget stopped working for me recently after it had been fine before. Similar setup to yours.
It bothered me a little but since the widget isn’t actually very useful to me I didn’t care to invest more time to get to the bottom of it.
I have a docker forgejo runner for CI with Codeberg. Where did you get stuck?
Short blogs with few but high quality articles are actually the salt of the earth.
I encourage you to do it, there are many options like Hugo, and your intellectual property will never be locked in a company’s app store (Prusa seems trustworthy for now, but as we’ve seen, lockout is always just a TOS change away.)
You already have the writeup and hosting a static site on github pages or similar doesn’t incur costs, so the only thing you need is some time and a domain. 🙂