Fix build.rake to use relative paths instead of absolute paths

[yann120]

WHY are these changes introduced?

Fixes #108

When deploying to a production environment (on fly.io with Linux), the application encounters a Errno::ENOENT error related to a symlink pointing to index.html in the public/dist directory. This symlink is generated correctly in a local Mac environment but fails in production due to its absolute path.

WHAT is this pull request doing?

This pull request modifies the Rake task responsible for generating the symlinks to use relative paths instead of absolute paths. By using relative paths, the symlinks become more portable and are less likely to break when deployed in different environments. The path will not the the one of the laptop where the build was made

(If applicable, attach before/after screenshots to visually showcase the change)

Checklist

Note: once this PR is merged, it becomes a new release for this template.

• I have added/updated tests for this change
• I have made changes to the README.md file and other related documentation, if applicable

[github-actions]

This pull request is stale because it has been open for 60 days with no activity. It will be closed if no further action occurs in 14 days.

[github-actions]

We are closing this pull request because it has been inactive for a few months.
This probably means that it is not reproducible or it has been fixed in a newer version.
If it’s an enhancement and hasn’t been taken on since it was submitted, then it seems other issues have taken priority.

If you still encounter this issue with the latest version of this app template, please reopen using the issue template. You can also contribute directly by submitting a pull request.

Thank you!