suggestion: site name should be case insensitive

did:plc:qmrrelpkwx7r5fip75wwvgfa opened this Mar 28, 2026 2 comments
did:plc:qmrrelpkwx7r5fip75wwvgfa opened Mar 28, 2026

Thanks to a f# up of my own, I came to the realization that the site name argument for the Wisp CLI is case sensitive, and the back-end is as well. This means that mySite, MySite, and mysite would be 3 different Wisp sites.

Unbeknownst to past (5 minutes ago) me, this was what was keeping me randomly raging at my Tangled pipelines... I kept adding build parameters and removing files to make sure I wasn't hitting limits. Until I opened the Wisp dashboard and noticed I had 2 similarly named sites. One capitalized and one not...

I had initially created the site with a capital letter, as in a title, but used lowercase in my config (because of habit with parameters). So for the past few days, I kept deploying my "fixes" to a totally different site I didn't realize even existed.

Since, in my personal opinion, it doesn't make a lot of sense to have e.g. mySite, MySite, and mysite; I want to propose to make site names case insensitive. By making all site names lowercase in the back-end, you wouldn't run into this issue anymore. Optionally the site identifier and site "title" could be made 2 separate fields in the database such that users can still pick a cased title, while in the back-end the "identifier" would be lowercase.

No activity yet.

cospan · schematic version control on atproto built on AT Protocol