Hi, I just started using the application and I’m already having problems as a newbie.
I can’t figure out why images or scripts added by the “library manager” aren’t loading when they’re located in the “/.fs/…” path.
Hmmm for what i see, with time the images is loading now
But i don’t understand, in de momento an 1hour after i uploaded and it was not working and now 1 day affter it’s working
For more information in my setup.
I using docker compose for silverbullet
services:
silverbullet:
image: Package silverbullet · GitHub
restart: unless-stopped
#user: 3007:3007
networks:
- Internal
environment:
- SB_USER=admin:admin
volumes:
- Biblioteca:/space
#ports:
# - 3000:3000
networks:
Internal:
name: Internal
external: true
volumes:
model-cache:
Biblioteca:
driver: local
driver_opts:
type: nfs
o: addr=192.168.1.25,rw,noatime,rsize=8192,wsize=8192,tcp,timeo=14
device: “:/mnt/Mirror/DATA/Docs”
for access de web i use the proxy nginx
in this i enabled cache assets, websockets support and block common exploits.
If someone could give me a little help and explain this to me, I would be very grateful.
what do you mean by files put in the /.fs/ you mean uploaded through silverbullet upload command or put it directly in the /space folder of silverbullet?
/.fs/ is the root folder and it is the same as / in the browser(for pages).
you’ve essentially built a digital waiting room. The reason your files take a day to show up isn’t ‘magic’, it’s because you’ve paired a slow NFS mount with Nginx asset caching. You’re effectively serving yourself stale 404 errors until the cache finally decides to check the disk again.
If you want your setup to actually work, try to do this:
- Kill the Nginx cache for the /.fs/ path immediately. It’s doing more harm than good here.
- Stop being surprised that a network share (NFS) isn’t snappy. You’ve got attributes caching on the mount and a proxy caching on top of that. It’s a miracle it works after only a day.
Either move your data to a local volume or tell Nginx to stop ‘helping’ you by caching files that haven’t even synced across your network yet. as far as i understood your setup. if not you could try to find the wekbpoint of your setup by fabricating a lab scenerio with a simplest setup.