Currently, if a founder wants to add a new connection (e.g., GitHub, Gmail) after the initial freeturtle init, they have to either manually edit the .env file or re-run a complex setup process.
Proposed Solution:
Implement a freeturtle connect <provider> command (e.g., freeturtle connect github) that:
- Runs the specific connection logic for that provider.
- Updates the
.env file.
- Offers to update
config.md to enable the module.
This makes the onboarding and expansion experience much more modular and less intimidating.
Currently, if a founder wants to add a new connection (e.g., GitHub, Gmail) after the initial
freeturtle init, they have to either manually edit the.envfile or re-run a complex setup process.Proposed Solution:
Implement a
freeturtle connect <provider>command (e.g.,freeturtle connect github) that:.envfile.config.mdto enable the module.This makes the onboarding and expansion experience much more modular and less intimidating.