...
Monorepo project structure needs to be considered.
Options considered
OptionSchema | flagbase.com | flagbase.com | flagbase.com | flagbase.io | Description | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Pros and cons | ||||||||||||||||||||||||||||
Estimated cost |
|
|
|
|
Action items
...
/<workspace>/<project> | |||
---|---|---|---|
Pros / Cons | Provides the “personal” feeling. Fairly easy to set up. Need to reserve a bunch of workspace ids so users are not able to take them. | Easy to implement Hard to manage cookies. | Easiest to implement Tried and tested 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
Implement schema 1.