Skip to content

Credits drain#835

Open
daschuer wants to merge 2 commits intomixxxdj:mainfrom
daschuer:credits_drain
Open

Credits drain#835
daschuer wants to merge 2 commits intomixxxdj:mainfrom
daschuer:credits_drain

Conversation

@daschuer
Copy link
Member

This enables client sice caching and stops building manual for old versions.
This shall safe 50 % of bandwidth and request and shall save use 15 € / month.

@ronso0
Copy link
Member

ronso0 commented Jan 21, 2026

I have no web dev knowledge, but summary by Perplexity re the css/toml changes, so looks good I guess, letÄs give it a try 🤷‍♂️

https://www.perplexity.ai/search/what-effect-do-the-following-c-1dOMkVuQRruf_9sh_lducw#0

@mixxxdj/developers is someone else more familiar with this stuff?

@ronso0
Copy link
Member

ronso0 commented Jan 21, 2026

stops building manual for old versions

You me re-build as we don't update old branches anymore, right?

@daschuer
Copy link
Member Author

No I mean to take them temporarily offline, to save bandwidth and access rates. My intention is to only have 2.5 and 2.6 online until the root cause of the hosting costs is fixed.

40 % of the traffic goes to old versions. Maybe just because of old Google indexes.
Here is also a pending work to have a static "current" link and allow that only that is indexed by web crawlers.
All that will take some time, just remove the $ penalty for the meantime.

Copy link
Member

@JoergAtGithub JoergAtGithub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have enough money to keep our services running until we selected a new webhoster. There is no immediate reason to remove the pages which our user access often.

@daschuer
Copy link
Member Author

daschuer commented Jan 21, 2026

To clarify, this PR takes down the manuals for Mixxx
1.11 - 2.4.
The current manual for 2.5 and upcoming 2.6 will be available as usually. If users are still on Mixxx 2.4, they can consult the PDF version of the manual or just use a more recent version. This is recommended anyway.
No need to spend contributed money to an not recommended not supported setup.

[[headers]]
for = "/**/*.js"
[headers.values]
Cache-Control = "public, max-age=31536000, immutable"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at the current transfer, should we also add *.png from the _static/ folder?

Image

Also, I am wondering if we should add a default somewhere between30 or 300. Arguably, when we test new deployment, it comes from a new environment, so cache will be cold, and if one wants to check the main website right after a change, they can always SHIFT+F5 to clear the cache.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no experience with this. My original Idea was to fix low hanging fruits.
To "buy" some time for the hoster change.
But if we are able to do the switch within on or two month we can do such things step by step with benchmarking and usability test later.

smv_tag_whitelist = r"^$"
smv_branch_whitelist = r"^(main|(\d+)\.(\d+))$"
# smv_branch_whitelist = r"^(main|(\d+)\.(\d+))$"
smv_branch_whitelist = r"^(?:main|2.5)$"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this change do?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This only build the main and 2.5 branch.
Skips the unsupported Mixxx version legacy.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are pages high ranked by search engines - otherwise they wouldn't have so much hits - blocking them would prevent new users from Mixxx.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants