Support Docker Volumes for Configurable Error Pages about error-pages HOT 5 CLOSED

Hello there,

Thank you for providing a detailed explanation of your issue! Currently, I'm working on a new major version of error-pages. Once the work is complete, I'll ping you here, and I hope you'll be pleasantly surprised by the new approach to handling custom templates 😉

from error-pages.

Hello there,

Thank you for providing a detailed explanation of your issue! Currently, I'm working on a new major version of error-pages. Once the work is complete, I'll ping you here, and I hope you'll be pleasantly surprised by the new approach to handling custom templates 😉

Does this mean that this was kinda useless of me? https://github.com/Its4Nik/NGX-Error

I added a custom github action that builds every theme there is and pushes it to ghcr.io

from error-pages.

Does this mean that this was kinda useless of me?

¯\_ (ツ) _/¯

Even if you only found your solution useful - it makes sense, right?

from error-pages.

Does this mean that this was kinda useless of me?

¯\_ (ツ) _/¯

Even if you only found your solution useful - it makes sense, right?

Yeah ig :)

from error-pages.

I could try to answer your question at #288 (comment) here

How can I configure my Traefik and replicate this into the new V3 error-pages docker container setup so that the static assets for the error pages are served correctly without being 403 forbidden? Any insights or suggestions would be greatly appreciated.

The error-pages project was designed to operate with error pages as single HTML pages, without loading additional resources from additional css or js files. This constraint simplifies deployment and usage, avoiding the challenges you've encountered.

The compose.yml file in this repository is intended only for local development and testing. Please do not refer to it when looking for solutions to use the project in your actual use case.

Is it possible for you to embed the content of every css and/or js file into a single HTML file, including images and everything you need for your error pages? If so, this might solve your problem (if I understood it correctly). You can then mount your template and specify the error-pages to use it, as mentioned in the readme file.

from error-pages.