a Blazor server app on MacOs is just a command line utility. build with
dotnet publish -r osx-x64
this will create folder with a command line app, and website folders. if you don't want the user to install the dotnet runtime, publish a self contained.
you can copy this folder to a mac or linux, and run the application, then in browser localhost:<port>.
now you just need to decide how to deploy to the application. VS only supports folder copy to webserver or file location.
For mac, you can also build a bundle for the app (on mac a bundle is a self contained folder that is a single file) and just copied to the users computer. you can make a dmg, that they download, and mount. also home-brew is an option.
For Linux, there are two install system based on the linux branch. apt-get or yum. You can probably find 3rd party or open source help to create these packages.
once you have deployed to the users computer, how will they run the app?
on a mac you can use launchctl as a startup application, so it is always running. then the uses just accesses with the browser. or you could create a script that starts the app if not running, then open in the browser.
the steps are similar for linux, except you use systemctl instead of launchctl (MacOs is berkley unix).
if you want to use ngnix or apache, you configure these are reverse proxies to the running app.