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

Migration to GeoKrety.org v2 - Partners testing #754

Closed
27 of 42 tasks
Tracked by #618
kumy opened this issue Oct 14, 2022 · 2 comments
Closed
27 of 42 tasks
Tracked by #618

Migration to GeoKrety.org v2 - Partners testing #754

kumy opened this issue Oct 14, 2022 · 2 comments

Comments

@kumy
Copy link
Member

kumy commented Oct 14, 2022

Hi,

I'm pleased to announce that GKv2 (GeoKrety.org rewritten from scratch) has now reached enough maturity in it's core public features to declare it as ready to be deployed. GKv2 work has been started some years ago, it's a complete rewrite, but the UI should look familiar. Sure there will be missing features but I think it's really usable.

The public staging instance is hosted at https://new-theme.staging.geokrety.org/. Database is synchronized from production every days at 2am UTC. So there will be no problem if tests are made there, just remind that everything there is volatile.

  • Bugs should be reported on GitHub.
  • Translations are hosted on crowdin.

Regarding the API and legacy URLs, I did my best to keep same API endpoints or add redirections so the migration should be transparent.


Partners are however requested to test their product on their staging/development environments against GKv2 using the url above ^^ before we proceed with the migration.


The migration date will be set depending of the quantity, severity and time need to fix the new found bugs. :) Due to database and schema changes, the GKv1 to GKv2 migration will be one way forward. The expected downtime should be around 6h. To give everyone enough time let's plan that for February/March 2023...

Known changes

Rate limit system

API endpoint now have 2 types of rates limits:

  • Use nginx rate-limiting and limit the number of request per second per group of endpoints
  • Authenticated endpoints have requests limits calls per days.

Both of them should be quite high. Let me know if some needs tuning. For the 2nd point, for each request you'll find in the headers the current consumption, limit and count period.

Timezone support

Historically all date times were processed as if they were UTC. Now timezone should be handled properly. On legacy API endpoints, there is now a new timezone parameter (default to UTC)

GKM/GK fusion

On migration, the api.geokretymap.org will point to api.geokrety.org

Pictures

  • Upload is now possible via drag&drop
  • Automatic image scaling
  • User can have multiple avatars

Comments

  • Unicode support in titles and message body 🎉

Missing features

  • Rate Geokrety
  • Races
  • Users statistics
  • GeoKrety statistics
  • No GeoKrety altitude profile

Bests
Kumy - GK Team - France


Notifications:

@okainov
Copy link
Member

okainov commented Sep 16, 2023

As usual we're very last minute :)

So after migration it looks like we have some issues with the full sync with geocaching.su against GK database. Incremental sync works fine via https://geokrety.org/export_oc.php?modifiedsince=%s endpoint, but we also do full refresh once in a while via https://api.geokrety.org/basex/export/geokrety.xml. And the latter gives 404 now.

Any suggestions for alternative endpoint returning full database dump?

Upd: ok, seems like I've found it in API documetnation page, updated the url to https://cdn.geokrety.org/exports/geokrety.xml and it looks fine now (seems like there was also some change about missing property, now it's not always available, but it's an easy fix on our side).

Thanks!

@kumy
Copy link
Member Author

kumy commented Sep 17, 2023

GKv2 deployed, closing

@kumy kumy closed this as completed Sep 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants