Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proxy Path #12

Open
AndreGuerra123 opened this issue Feb 1, 2024 · 2 comments
Open

Proxy Path #12

AndreGuerra123 opened this issue Feb 1, 2024 · 2 comments

Comments

@AndreGuerra123
Copy link

Hi,

Currently, I need to add a proxy pass (designation under nginx) to /api, common in most vuejs projects. My case is to a external URL. Is this possible and how to do it?

@maybeanerd
Copy link

maybeanerd commented Feb 17, 2024

AFAIK this replaces nginx to serve static assets, not as a reverse proxy. If you want to use another reverse proxy than nginx, try out https://traefik.io/traefik/

In general you would have a setup similar to
traefik
->backend (some image)
->frontend (served by this image)

and have traefik control what paths point to where

@ivictbor
Copy link
Contributor

ivictbor commented Feb 21, 2024

Yes, exactly, spa-to-http is generally designed for use with Traefik or when you have no proxy at all. Traefik is simpler and easier to manage in most use-cases then Nginx. It has a lot of nice features like very simple and free HTTPS(SSL) setup (Example).

So in general a lot of developers used Traefik for proxying API/complex schemes, but served SPA bundles with things like Nginx (in combination with Traefik). So we creates SPA-to-HTTP as dedicated and faster alternative to Nginx, which again could be used in combination with Traefik. You can read detailed Traefik vs Nginx comparison guide, there we explained why we switched most of our projects at Devforth to Traefik.

Also I would recommend blog post about spa-to-http initial usecases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants