Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid processing config when serving from overlay directory #114

Open
stelcodes opened this issue Aug 18, 2022 · 0 comments
Open

Avoid processing config when serving from overlay directory #114

stelcodes opened this issue Aug 18, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@stelcodes
Copy link
Owner

stelcodes commented Aug 18, 2022

Currently all requests for CSS/JS/whatever from the overlay directory cause the config to be loaded every time. This is wasteful and produces obnoxious log messages like:

18:18:52 INFO ⚑🐈 Rendering page:
{:nuzzle/get-config
 #function[nuzzle.generator/gen-get-config/get-config--5558],
 :nuzzle/index
 #{[:blog-posts] [:tags] [:coding-projects] [:educational-media]},
 :nuzzle/page-key [],
 :nuzzle/render-content #function[clojure.core/constantly/fn--5740],
 :nuzzle/title "Home",
 :nuzzle/url "/"}
18:18:52 INFO πŸ”¨πŸˆ Building drafts
18:18:52 INFO πŸ”¨πŸˆ Building drafts
18:18:52 INFO πŸ”¨πŸˆ Building drafts
18:18:52 INFO πŸ”¨πŸˆ Building drafts
18:18:53 INFO πŸ”¨πŸˆ Building drafts
18:18:53 INFO πŸ”¨πŸˆ Building drafts

Avoiding this is tricky. I probably need to try serving every page from the static directory ring middleware handler first and check if the status is a 400 or similar.

@stelcodes stelcodes added the enhancement New feature or request label Aug 18, 2022
@stelcodes stelcodes changed the title Avoid building config when serving from overlay directory Avoid processing config when serving from overlay directory Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant