Yeah, I know about the proxy in vue-cli, but the problem I don't want to use this Node.js server in production, so I build the vue project and Go will be the static fileserver. For development, the webpack based proxy server in vue-cli is fine though.
I can implement a proxy in Go which is exposing the api server within the static server (under a route like /api/v1, this way I can use relative urls in axios), but my problem with this approach is that the static server is not only serving the static files in this case, it's doing a little bit of backend work also. Which I try to ignore, because what if the static files hosted on AWS?
Why don't you just deploy the build of the SPA to the go server so it can serve it?
I'm not using Node as a server, just for development. I have a post build command that builds the static files so that the Python server can send them to the client.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank You!
Yeah, I know about the proxy in
vue-cli, but the problem I don't want to use this Node.js server in production, so I build the vue project and Go will be the static fileserver. For development, the webpack based proxy server invue-cliis fine though.I can implement a proxy in Go which is exposing the api server within the static server (under a route like
/api/v1, this way I can use relative urls inaxios), but my problem with this approach is that the static server is not only serving the static files in this case, it's doing a little bit of backend work also. Which I try to ignore, because what if the static files hosted on AWS?Why don't you just deploy the build of the SPA to the go server so it can serve it?
I'm not using Node as a server, just for development. I have a post build command that builds the static files so that the Python server can send them to the client.