(?) How To: Deployment of Kirby Changes to Vue

[Maybach91]

Hej,

thanks for the awesome work setting up this awesome starterkit!

I have one question: You are suggesting deploying the content of kirby to the production server. So if i have kirby.domain.com for the Editor to build the content. How should we handle changes within the kirby system to the Frontend / Vue (nuxt)? Do you have any suggestions @jmheretik ?

Thanks for your ideas in advance!

[johannschopplich]

@Maybach91 Shamelessly plug for my kirby-vue3-starterkit, which once built upon @jmheretik's work. He seems quite busy at the moment. My starterkit has detailed documentation, as well on how to deploy in production. Maybe worth a look!

[Maybach91]

@johannschopplich thanks! i will try to transfer it to your project. I mean, i got it kinda working, but deploying to vercel does not works with the routes. i cannot access the subpages directly. :/

[johannschopplich]

Both starterkirs aren't suited for Vercel, I presume. Or do they support serving PHP projects?

[Maybach91]

Yea, there are some workarounds/runtimes for using php on vercel. But what i tried with vercel was just deploying the nuxt version of this repo. But got failed but no have direct access to the subpages on reload, since it always deploys the SPA version. Dont know why/how tho. I don’t know, if this is related to #19

[jmheretik]

Im not sure I understand the question... If you're making changes to your content then no modifications are required on the frontend side, that's the point of CMSs 😉. But if you're changing kirby blueprints or templates you should also change your frontend (vue) components/templates to accomodate those changes. After you're done adjusting everything locally, you build the project and upload the whole kirby folder to your hosting.

If this didn't help, can you be more specific about your problem please?