Versions Compared

Old Version 1

changes.mady.by.user Chris J

Saved on

compared with

New Version Current

changes.mady.by.user Chris J

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page Properties
label

Status

Status
colourYellowGreen
titleIn progressDONE

Impact

Status
colourRed
titleHigh

Driver

Chris J 

Due date

Outcome

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

...

  • Monorepo project structure needs to be considered.

Options considered

SchemaOption

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

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

flagbase.com
app.flagbase.com

flagbase.io

Description

Pros and cons

(plus)

(minus)

(plus)

(minus)

(plus)

(minus)

(plus)

(minus)

Estimated cost

Status
colourRed
titleexpensive

Status
colourRed
titleexpensive

Status
colourRed
titleexpensive

Status
colourGreen
titlecheap

Action items

...

/<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.