@Marvin how can i update the url used in Prefect 2's notification framework for a self hosted server, e.g. switch

localhost:4200

here to by the ingress for my server

<http://localhost:4200/flow-runs/flow-run/dcdc561c-7665-42bc-a018-8f15fb231f98>

It looks like the current Prefect 2.x documentation doesn't provide a specific method to update the URL used in the notification framework directly from within Prefect's configuration settings. Typically, Prefect uses environment variables or configuration settings to specify the URL for its server or UI. For a self-hosted server, you would typically update the base URL in your server's configurations or environment settings where Prefect is deployed. Here is what you might consider doing: 1. Update Environment Variables: If your deployment is configured through environment variables, check for a variable that specifies the Base URL or the UI URL, and update it accordingly. 2. Configuration Files: If your Prefect server is configured using a configuration file (YAML or JSON), look for an entry related to the URL or HTTP settings and update it. 3. Reverse Proxy or Ingress: If you're using a reverse proxy or ingress to expose your service, ensure that it's configured properly to rewrite URLs as needed to access your server using the desired domain. 4. Notification Services: If you're using external notification services like Slack or Email through Prefect, ensure that these are configured with the correct URLs pointing to your server's ingress. For further assistance, you might need to consult with your network or systems administrator who manages your Prefect deployment environment. To get started with these adjustments or for more specific steps, you may want to refer to the Prefect Deployment documentation or seek guidance from community forums where others have dealt with similar self-hosted configurations. If you want to explore more documentation, you can start here.