-
-
Notifications
You must be signed in to change notification settings - Fork 19
Deployment: What and how? #37
Comments
Hey Florian, thanks for the flowers! Regarding deployment, what service do you use? This starter kit follows the public folder setup. Pretty common in the Laravel universe as well. Clone your whole repository and tell your web server the project web root is If you're setting up your server configs manually, say for Nginx, you can use the root key: server {
# Directory to serve files from
root /var/www/getflourish/public;
} On shared hosters like Uberspace, you can just clone your repo and create a symlink to the |
thanks for this cool Starterkit! I followed your last advice to quickly check how the deployment would work. Simply uploaded all data after the build command on a shared hosting directory (LAMP no node), adjusted the domain routing and voila could access the Kirby panel – but the frontend would not load properly. Investigating with the console showed, that script tags in < head >, generated by kirby-vite are pointing to localhost:3000. <script src="http://localhost:3000/@vite/client" type="module"></script> <script src="http://localhost:3000/main.js" type="module"></script>I assume that is the value for DEV mode. But I don't understand why. Did I miss something? I even added KIRBY_MODE=production to the .env Many Thanks |
@jtackmann I recommend running the build command on the server, not locally. The The |
I also have a deployment issue. I tried to follow the instructions, cloned the entire repo (to an uberspace subdirectory),
Any idea, what could be causing this? Thanks! |
@trych What's your Node.js version? |
@johannschopplich |
@johannschopplich Ah sorry, I realize now this is quite an old one and Uberspace will easily allow me to pick a newer one. Sorry 🙈. Will give this a try. |
I recommend the latest LTS version, which is 16. Prior to 14 Node didn't has had ESM support. Thus, the build pipeline failed. 😊 |
Ok, it does build now with Node.js v16, but when I try to load the page it shows the title, but no content and gives me a bunch of 404 errors. Do I need to set something else? Is it maybe an issue that this happens in a subdirectory on Uberspace? I am just trying to directly open the site in I think it tries to access stuff on Also, do I need to change anything in |
You have to point your web server to the public directory. Speaking for Uberspace:
Now, when you open Of course you will have to register the domain via |
Hm, I think you misunderstand what I am trying to do. I don't want to serve this starterkit at the main domain But when I open that URL, it tries to access assets and other things at Does this make any sense? Is there any way to point these requests to the correct location? |
I see. Well, that's gonna be tricky. You will have to set the base URL for the Vue router and the backend routes maybe as well. Doesn't a subdomain equally serves your testing purposes? I recommend just creating |
That might be an idea. Will look into how to serve a folder to a subdomain on Uberspace. Thanks! |
Hi! Thanks a lot for this great Starterkit, love it!! 🌸🌸🌸 A quick question about deployment: I managed to deploy the project to my uberspace, it's in a subfolder, so the domain looks like this:
and it works fine for the panel! The frontend however throws an error when the Javascript is trying to fetch data from the Kirby API and I can see that it's trying to fetch it from
So here comes my question: how can i tell the Javascript that the Kirby API is available under vuekirby/app instead of /app ? Thanks a lot! |
@jonasholfeld Thanks for the flowers!
|
That did the trick, thanks a lot! |
trying to put template online :) web dIrectory already on Example error:
Those file dont exist at all so I dont know how to find their real address. Should I rebuild some special setting? can you help me find the real adresse for the backend? this is the working link where im putting up the template: https://site.lumbungradio.org/ |
Developing a site with this Starter Kit was super nice, especially with the newer versions that even come with automatic component imports etc. Thank you!
Now it’s time for deployment, but I don’t understand how.
As far as I understood, Node is not required on the server, but only to build the frontend, right?
From the README:
public
or just the contents ofpublic
? What does "point your server topublic
" mean?I’ve tried a couple of things but I’m clueless how this should work.
The text was updated successfully, but these errors were encountered: