Ticket: Images not accessible on localhost:4200/uploads
@cao Just created a ticket
Question: After upload new images, i can access them in vs code at the folder /uploads, but can't access them on localhost:4200/uploads/ ....
Attempted: error message: ⨯ uncaughtException: [Error: ENOENT: no such file or directory, open './uploads/2024/12/03/fb38444c33e7f534fb2f36472aa3f887.png'] { errno: -2, code: 'ENOENT', syscall: 'open', path: './uploads/2024/12/03/fb38444c33e7f534fb2f36472aa3f887.png' }
Working On: fixes for a PR
Using Postiz On: locally
Take it from here @Postiz
Question: After upload new images, i can access them in vs code at the folder /uploads, but can't access them on localhost:4200/uploads/ ....
Attempted: error message: ⨯ uncaughtException: [Error: ENOENT: no such file or directory, open './uploads/2024/12/03/fb38444c33e7f534fb2f36472aa3f887.png'] { errno: -2, code: 'ENOENT', syscall: 'open', path: './uploads/2024/12/03/fb38444c33e7f534fb2f36472aa3f887.png' }
Working On: fixes for a PR
Using Postiz On: locally
Take it from here @Postiz
7 Replies
So actually the backend doens't serve this
GitHub
postiz-app/var/docker/Caddyfile at main · gitroomhq/postiz-app
📨 The ultimate social media scheduling tool, with a bunch of AI 🤖 - gitroomhq/postiz-app
The container uses Caddy to serve the uploads directory
So if you need upload functionality in a local dev environment, use Caddy to serve that dir
well i need it to show images
any idea how to start Caddy locally ?
i already installed it
Yeah just create a "caddyfile" (like that link)
and "caddy run"
it's super friendly for developers
Need to go, good luck!
okay, will try it
thank u 🙂
Hi @cao Please select an action