Handling multiple ArNS updates/deployments

[kempsterrrr]

I recently opened a PR to add ArNS to Partick's localsafe - Cyfrin/localsafe.eth#48 (comment)

This PR included two deployments per update:

• Deploys to version-specific undername (e.g., v0-2-0_name.arweave.net)
• Deploys to root ArNS name for latest version

To achieve this permaweb-deploy deploys the site twice which is inefficient and adds costs, it also to a degree breaks the provenance story of these deployments there are two TxIDs for the same version.

Is it possible to add support to deploy to multiple arns names/undernames with the same TxID output for such use-cases?

[atticusofsparta]

I think the best way to handle this would be to introduce the concept of a permaweb-deploy.json file to configure these.

Something like

{
  deploy: {
    arnsName: "bob",
    createVersionedUndernameOnDeployments: true,
    undername: "alice",
    ttl: 60,
   ... other deploy flags
  },
  signing: { deterministic: true, wallet: { path: "~/wallets/publishing.json" } },
  include: [**/parquet/*, src/*, **/*/*.ts] // potential to include non built source files
}

And if you had different names your would just make different files like permaweb-deploy.ardrive.json or permaweb-deploy.arns.json for the specific deployment for the application.