Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Status

IN PROGRESS

Impact

HIGH

Driver

Chris J 

Due date

Outcome

What domain we will be using for the landing page & app.

Background

We need to decide where users will land when they first visit the website and when they try to log in to the app.

Relevant data

  • Monorepo project structure needs to be considered.

Options considered

Schema

flagbase.com
<workspace>.flagbase.com/<project>

flagbase.com
flagbase.io/<workspace>/<project>

flagbase.com
app.flagbase.com/<workspace>/<project>

Pros / Cons

(plus) Provides the “personal” feeling.

(plus) Fairly easy to set up.

(minus) Need to reserve a bunch of workspace ids so users are not able to take them.

(plus) Easy to implement

(minus) Hard to manage cookies.

(plus) Easiest to implement

(plus) Tried and tested

(minus) No “personal” feeling

Action items

  • Verify that you can redirect requests to subdomains to single app
  • Rename repo (flagbase)
  • Split out client SDKs into different repo (flagbase-client-sdks)
  • Rename frontend and website firebase hosted domains

Outcome

Deciding to go with using subdomains for multi-tenancy, as it gives the feeling of an isolated environment.

  • No labels