search

denoland / deploy_feedback

For reporting issues with Deno Deploy
https://deno.com/deploy
74 stars 5 forks source link

Allow Longer Project Names #721

Open rawkode opened 1 month ago

rawkode commented 1 month ago

What problem are you trying to solve?

I'm having to come up with systems to shorten and keep names of my micro service architecture understandable without a map.

A service in my architecture has multiple micro services. My user service has a unique and independent read layer, write layer, and integrations later.

When this was running on CF, my services where:

platform-user-read-production platform-user-write-production

And so forth.

Describe the solution you'd like

Allow up to 128 characters for project name

Describe alternatives you've considered

N/A

Documentation, Adoption, Migration Strategy

No response

arnauorriols commented 2 weeks ago

Hi! We cannot allow 128 characters as they need to fit within a subdomain, and subdomains have a 63 character limit. It has to be less than 63 characters because we have deployment subdomains (<project-name>-<deployment-id>) and branch subdomains (<project-name>--<branch-name>). However, as you say 26 characters is probably unnecessary restrictive. We'll bump the limit a bit 👍

rawkode commented 2 weeks ago

I don't know why I thought labels could be 128 characters, silly me.

Instead of project-name-deployment-id, could it be deployment-id.project-name?