Nuxt project build got triggered 2nd times
Currently I'm trying to get the AgencyOS from Directus work, but so far got a lot of troubles. After a sleepless night, I managed to make the backend worked. Now the frontend has issue.
Please don't get me wrong, this is not complain, for example the issues in the backend of directus come from their side! Dokploy works perfectly here. I guess the frontend issue could be the same.
But we have more reactive response here, that's why I'm trying to seek helps here (while waiting for Directus response)
My current issue is the build of Nuxt. I guess it is resources intense just like Next.js, whenever I hit the deploy button, the whole server got lagged and sluggish noticable! Another thing I find it strange, is after the first deployment running for a couple minutes, another record appear! Please check the screenshot.
What would you think might cause it?
Dokploy 13
Directus template: https://github.com/directus-labs/agency-os
Steps I have done:
- Used the official Dokploy's Directus template as backend.
- Run the
npx directus-template-cli@0.4.3 apply
(latest version does not work)
- Use the github repo above as frontend, build with nixpacks, default configs.
1 Reply
🤔 I think I found out my mistake: I used the incorrect url for SITE_URL and DIRECTUS_URL, after set it correctly things work now. Sorry for false alarm.
And no, Nuxt is built much much faster than Next. Sorry Nuxt for comparing you with Next.