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

[CDN URL] Update fallback CDN path... #4877

Closed

Conversation

chromoxdor
Copy link
Contributor

I changed the path to a more generic URL as suggested here: jsdelivr/jsdelivr#18541

@chromoxdor chromoxdor changed the title Update fallback CDN path... [CDN URL] Update fallback CDN path... Nov 17, 2023
@chromoxdor
Copy link
Contributor Author

Just realized that it was already changed..
Thanks @TD-er !

@chromoxdor chromoxdor closed this Nov 23, 2023
@chromoxdor
Copy link
Contributor Author

I somehow not quite awake :)
i thought you changed it in your PR but you didn´t...

@chromoxdor chromoxdor reopened this Nov 23, 2023
@TD-er
Copy link
Member

TD-er commented Nov 23, 2023

Not sure if it should be only in the Python file.
If built using Arduino IDE, then no Python file is used.

Ton has a PR which allows to specify a user defined URL.

@chromoxdor
Copy link
Contributor Author

Ton has a PR which allows to specify a user defined URL.

will test that when i am finished testing his WiFi PR.
Did he implement a fallback URL when non is given?

@chromoxdor
Copy link
Contributor Author

Or better asked, where is it directing to when pygit2 is missing? As far as is could see this is not part of his PR...
or is it intended to be the part where i enter afterwards my own fallback URL?

@tonhuisman
Copy link
Contributor

Currently it would use this fallback implemented in CompiletimeDefines.cpp if pygit2 is not available (AFAICS) or Arduino IDE compilation is used.

@chromoxdor
Copy link
Contributor Author

ahh.. i see, thanks.

// FIXME TD-er: Not sure which is better, serving the latest (which will have caching issues) or a tag which will become outdated

I vote for latest. :) (When i freshly make a build i expect to have the latest files)

@TD-er
Copy link
Member

TD-er commented Nov 23, 2023

ahh.. i see, thanks.

// FIXME TD-er: Not sure which is better, serving the latest (which will have caching issues) or a tag which will become outdated

I vote for latest. :) (When i freshly make a build i expect to have the latest files)

Yep, but the 'latest' will be whatever your browser has in its cache.
So your expectation will probably not match with what you get.

@chromoxdor
Copy link
Contributor Author

Yep, but the 'latest' will be whatever your browser has in its cache.
So your expectation will probably not match with what you get.

But to fix this i only have to do a hard refresh of the site. The other option would force me worst case to upload a new adjusted firmware.

@chromoxdor chromoxdor closed this Nov 24, 2023
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.

3 participants