2 months ago
Hi, we have a system dependency on Typesense.
It looks like the current official Typesense Railway template is not the latest/stable version - can we get it to the latest version?
4 Replies
Status changed to Open Railway • 2 months ago
2 months ago
Hello,
the railway template dockerfile is hardcoded to typesense/typesense:29.0 but the latest stable release is 30.1. just bumping the dockerfile from 29.0 to 30.1 will fix it
also the v30 has a breaking change: synonyms and curation rules are no longer nested under collections, they're now top-level resources. existing data gets auto-migrated on upgrade, but any api keys scoped to synonyms:* or overrides:* actions will need to be recreated with the new synonym_sets:* / curation_sets:* actions
Hope this help you :)
domehane
Hello, the railway template dockerfile is hardcoded to typesense/typesense:29.0 but the latest stable release is 30.1\. just bumping the dockerfile from 29.0 to 30.1 will fix it also the v30 has a breaking change: synonyms and curation rules are no longer nested under collections, they're now top-level resources. existing data gets auto-migrated on upgrade, but any api keys scoped to synonyms:\* or overrides:\* actions will need to be recreated with the new synonym\_sets:\* / curation\_sets:\* actions Hope this help you :)
2 months ago
thanks, @domenhane - i think the ask here is to get confirmation / verify the changes on Railway template itself, running on Typesense ona Railway instance.
I understand the application-level behaviour change - good to know that they get auto-migrated!
a month ago