Hey @Pallavikumarimdb sorry to close another one... Having given this thought we think we want to do two things:

• The recommended way to manage multiple domains for now is to create multiple resources. This is because in many places we look up the resource by its domain, and making this many to one would have some cascading issues. We want to tackle it in the future but dont think it is time with other higher priority features and dont want this work to go stale.
• Creating a separate side bar page and table for redirects. Here the user will create redirect items in the table that will take in a source and redirect to a destination. This would be generalizable across resources or external things as well.

Ill talk with you soon about 2nd one.

@oschwartz10612 What's the status on this? I was considering working on it, but read through yours and @P6g9YHK6 (and other's discussions) on this feature. This is a must-have feature for me coming from NPM. Currently I'm having to create identical resources for www.domain.tld and domain.tld which is just silly imo.

@mattv8 we plan to add a way to create a redirects table to redirect urls to resources or even other urls. Should come up soon.

Multiple domains per resource not sure about yet because it has a implication across the whole application.

Sounds good! If there's anything I can do to help (QC a PR) lmk 👍