Problem moving from default Turboku deploy to our own config

Hi,
Background:
I’ve recently migrated several of my customers sites (Nuxtjs with SSR) from Heroku to Fly using the Turboku tool. The migration itself went great and we’re very happy Fly.io customers :).
Today I wanted to do the first update on one of our since the migration, but for unclear reason Fly does not seem to pick up and mirror new deployments in Heroku. But I think I saw on other threads here on the forum that its recommended to move to direct Fly deployment regardless.
Problem:
So I’ve been trying to create a fly.toml and get it setup with our gitlab ci. It seems that I’m close but I keep getting some error right on the finish line. The build steps goes well but the app fails to start with the following error:

2022-10-13T13:17:12Z   [info]yarn run v1.22.19
2022-10-13T13:17:12Z   [info]$ nuxt start
2022-10-13T13:17:14Z   [info] FATAL  No build files found in /workspace/.nuxt/dist/server.
2022-10-13T13:17:14Z   [info]Use either `nuxt build` or `builder.build()` or start nuxt in development mode.
2022-10-13T13:17:14Z   [info]  Use either `nuxt build` or `builder.build()` or start nuxt in development mode.
2022-10-13T13:17:14Z   [info]  at VueRenderer._ready (node_modules/@nuxt/vue-renderer/dist/vue-renderer.js:758:13)
2022-10-13T13:17:14Z   [info]  at async Server.ready (node_modules/@nuxt/server/dist/server.js:637:5)
2022-10-13T13:17:14Z   [info]  at async Nuxt._init (node_modules/@nuxt/core/dist/core.js:482:7)

Questions:

  1. Is there any way to find out what configuration/fly.toml etc that Turboku used since it works well to deploy using that tool?

  2. Does anyone have previous experience with Nuxt.js v2 on Fly.io and that could help and post their fly.toml/Procfile?

Thank you in advance for any help.