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

Redirects in YAML #4221

Open
agjohnson opened this Issue Jun 11, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@agjohnson
Copy link
Contributor

agjohnson commented Jun 11, 2018

We brought up the idea of using our YAML file for redirects. There are a number of problems with this though, as well as many existing problems.

Current problems:

  • If the application is down, redirects don't work
  • If we wanted to make a Azure storage hosted version, we don't have an application or ngnix to fall back on for redirects
  • Redirects are project level currently

New problems:

  • Keeping per-version redirects in YAML makes a lot of sense, but per-project redirects are still valid and do not make sense in YAML
  • Because of ^ we need 2 sets of redirects -- the UX would probably be to make current redirects "Project Redirects"
  • Making per-version redirect model is okay, as we can update the database per-version on build, but the point above about azure redirects is valid still.

So, design decision looks a little like this:

  • Does azure support some method of hosting files and providing redirects (and not http meta redirects)?
  • If not, is hosting files directly from storage the right solution? If not, perhaps a load balancer and nginx sort of situation makes sense in front somehow?
  • If azure does support this, how do we do config file redirects -> ? -> azure redirect?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.