config.toml does not match on old (and new) projects
Been trying to solve this for a minute now, i have been trying to link my local work to my remote project but regardless of what I do I keep getting a config.toml mismatch. Seems to be affecting other people too. Any ideas on how to fix it? The Github issue here is pretty much my exact issue, I can't even resolve all the diffs...
https://github.com/supabase/supabase/issues/32416
GitHub
Config does not match · Issue #32416 · supabase/supabase
Bug report [ X ] I confirm this is a bug with Supabase, not with my own application. [ X ] I confirm I have searched the Docs, GitHub Discussions, and Discord. Describe the bug It's not possibl...
4 Replies
Seems like there is an issue right out of the gate when trying to init a supabase project; would be a pretty big issue. The local -> remote
config.toml files don't match and the diffs cannot be fixed. I'm wondering it's somehow just my machine.
Anyone willing to stand up a new project, create a new supabase project locally, and then try to supabase init and connect to their remote?
note: removing additional_redirect_urls from my config.toml file is not detected between attempts. Other keys are detected, but any changes to this specific one go unnoticed (same issue discovered in the above github issue).
I've taken to ignore the warning that the configs are different upon running the link command. Of course they are! One is development and one is staging/preview. They by definition have different configs. It also doesn't differentiate between differences that affect supabase operation (like the auth minimum password rules) or things that don't like the SMTP settings (which must be different). I think this is a really poorly thought out feature -- there's no obvious pattern for managing multiple remote environments from a single local config file.
Good to know, it didnt really make a ton of sense to me. Thanks for the insights!