Tim Ermilov

There's currently no way to do that for all deployments (unless I'm missing something and traefik allows defining "default" middlewares). The only way would be to all labels manually to...

Updated the ticket to reflect the feature! For now you can just add your middleware labels to `exoframe.json` to define that error middleware and then use it in config, i.e.:...

I'd simply create a new exoframe deployment for that apache with one additional label (`"traefik.http.services.error-page.loadbalancer.server.port=80"`)

Not at the moment 🤔

@smirnp I think that sounds as a useful additional feature. I'll change the ticket to feature and will try to ship it in 3.1 update. but yes, if you fork...

yes, this is correct

Currently Exoframe loads recipes from npm - hence when you execute `exoframe setup exoframe-recipe-hobbit` it pulls current version of recipe from there. You need to publish your own version either...

@dualizeo how would that help in updating project deployed with exoframe? 🤔

Moving docs to website would also allow updating them without rebuilding whole CLI which is nice.

@FDiskas all yours! Here's a repo for it: https://github.com/exoframejs/exoframe-website