Deployment?
-
How do you guys handle your deployments?
My current workflow feels a bit clunky.
- ‘quasar build’
- Open FTP to the subdomain folder for the app.
- Delete the existing app files (except for the .htaccess file).
- Upload new build from the local folder.
I am mainly making internal tools for a small group of users, so it is working so far… I’m just wondering if I am missing out on a better deployment strategy. I’m using SPA if that matters.
-
hmm, git or mercurial deployment?
-
I’m using docker for my deployment. After each push to the master branch, a new image is built and deployed to production. Inside docker, I’m running quasar build and quasar serve and all of that is running behind nginx-proxy also running in docker.
I’ve posted an image below, it might help you to get a picture of how things are running. Staging container is a clone of how my production is running.
https://github.com/jwilder/nginx-proxy
-
@qyloxe I’m using git. Since posting this, I’ve been made aware of Netlify, which seems like it could solve this problem for me (automating deployment based on bitbucket pushes), but so far I haven’t been able to get the build to register as successful.
I made this question about it on Stack Overflow: https://stackoverflow.com/questions/54772505/how-do-i-deploy-a-quasar-framework-spa-using-netlify
-
@Shone Thanks for the diagram, that’s a very interesting process. I’m currently just using production with no staging aside from local dev on my machine.
