Update to latest version

[shubhankartrivedi]

Just saw there is a new major version.

https://github.com/strapi/strapi/releases/tag/v5.0.2

[brody192]

@Milo123459 wanna take a look and see if the upgrade would be easy?

[ar-to]

Hello. First, thanks for creating this repo, really helped me get started with railwayapp. Wanted to share as its related to this issue. I did manage to successfully deploy strapi v5 to railwayapp and you can find it @ https://github.com/ar-to/strapi-backend. The main changes I noticed were:

• had to add a new env var to the strapi service in railwayapp DATABASE_CLIENT="postgres" to trigger the correct client. The docs mentioned that the DATABASE_URL is used in the connectionString connection which is enough to connect to the db. https://docs.strapi.io/dev-docs/configurations/database#connection-parameters

- found it important to ensure the correct node version is used and the package-lock.json is updated and released or you get missing package errors. Sounds obvious but its not. This threw me off a little while because I though it would build internal similar to other tools and not rely on the lock file. Maybe its just me but only ran into this via railwayapp and its use of nixpacks. Probably good to have but it was confusing to figure out with little to no docs. - disconnect this template from the railwayapp service like mentioned on the readme.

Thats it. Pretty cool actually once the simple things are figured out. Some suggestions:

• Maybe add screenshots to the readme to save a little time
• explain how the railwayapp link works or ask the devs to do that because I wanted to use it for my new repo to test but was not sure what it would do and did not want mess things up and waste more time. I did test it with this repo template and worked nice but it was not super obvious you have to pick the strapi service so make sure to emphasize and screenshot it to save time searching the docs.

I did consider making a PR but was in rush to get my project tested and it turned out to be faster to just start with a fresh v5 project than figure out what this project did. Hope this helps speed up update so others can use it.

I would consider upgrading to v5 important for reasons @ https://docs.strapi.io/dev-docs/migration/v4-to-v5/breaking-changes specifically https://docs.strapi.io/dev-docs/migration/v4-to-v5/breaking-changes/use-document-id which impacted my project. Not sure this template will be of much use soon without staying up to date.