Great question! I’ve walked through this exact setup on my own MacBook Pro running Big Sur, so let me break down the process step by step—no fluff, just actionable steps.

Prerequisites #

First, let’s make sure you have everything you need:

• .NET Core SDK: Verify it’s installed with this command (if not, grab the latest version from the official .NET release page):

  dotnet --version
  

• Apache: Big Sur comes with Apache pre-installed, but it’s disabled by default. Start it and confirm it works:

  sudo apachectl start
  

  Open your browser and go to http://localhost—you’ll see the "It works!" page if Apache is running correctly.

Step 1: Prepare Your .NET Core App #

Before configuring Apache, get your app ready for hosting:

1. Test locally first: Run dotnet run from your project directory and confirm your app/Web API behaves as expected.
2. Publish to a production-ready folder:

   dotnet publish -c Release -o ./publish
   

3. Verify the published build works: Navigate to the publish folder and start the app directly with Kestrel:

   cd ./publish
   dotnet YourAppName.dll
   

   Visit http://localhost:5000 (or your app’s configured port) to ensure it loads properly.

Step 2: Configure Apache as a Reverse Proxy #

Apache can’t run .NET Core apps directly—instead, it acts as a reverse proxy to forward requests to the Kestrel server running your app. Here’s how to set this up:

Enable Required Apache Modules #

Run these commands to enable modules needed for proxying:

sudo a2enmod proxy proxy_http proxy_html rewrite
sudo apachectl restart

Create a Virtual Host Configuration #

1. Create a new config file for your app in Apache’s sites-available directory:

   sudo nano /etc/apache2/sites-available/yourapp.conf
   

2. Paste this configuration (replace placeholders with your app’s details):

   <VirtualHost *:80>
       ServerName yourapp.local # Or a custom domain you’ve added to /etc/hosts
       ServerAlias www.yourapp.local
   
       # Reverse proxy traffic to Kestrel
       ProxyPass / http://localhost:5000/
       ProxyPassReverse / http://localhost:5000/
   
       # Optional: Serve static files directly via Apache (skip if you want Kestrel to handle them)
       # Alias /static /path/to/your/app/publish/wwwroot
       # <Directory /path/to/your/app/publish/wwwroot>
       #     AllowOverride None
       #     Require all granted
       # </Directory>
   
       # Logging setup
       ErrorLog "/var/log/apache2/yourapp-error.log"
       CustomLog "/var/log/apache2/yourapp-access.log" common
   </VirtualHost>
   

3. Save and exit the editor (Ctrl+O, then Ctrl+X in nano).

Set Permissions for Your App Folder #

Apache runs as the _www user, so grant it access to your published app folder:

sudo chmod -R 755 /path/to/your/app/publish
sudo chown -R _www:_www /path/to/your/app/publish

Enable the Virtual Host and Restart Apache #

sudo a2ensite yourapp.conf
sudo apachectl configtest # Check for syntax errors
sudo apachectl restart

If you used yourapp.local as the ServerName, add an entry to your /etc/hosts file:

sudo nano /etc/hosts

Add this line:

127.0.0.1 yourapp.local www.yourapp.local

Now visit http://yourapp.local—your .NET Core app should load via Apache!

Step 3: Auto-Start Your .NET Core App on Boot #

Right now, your Kestrel server will stop when you restart your MacBook. Use macOS’s launchd to run it as a background service:

1. Create a launchd plist file (replace placeholders):

   nano ~/Library/LaunchAgents/com.yourcompany.yourapp.plist
   

2. Paste this configuration:

   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
       <key>Label</key>
       <string>com.yourcompany.yourapp</string>
       <key>ProgramArguments</key>
       <array>
           <string>/usr/local/share/dotnet/dotnet</string> <!-- Verify path with `which dotnet` -->
           <string>/path/to/your/app/publish/YourAppName.dll</string>
       </array>
       <key>WorkingDirectory</key>
       <string>/path/to/your/app/publish</string>
       <key>RunAtLoad</key>
       <true/>
       <key>KeepAlive</key>
       <true/>
       <key>StandardErrorPath</key>
       <string>/var/log/yourapp-error.log</string>
       <key>StandardOutPath</key>
       <string>/var/log/yourapp-output.log</string>
   </dict>
   </plist>
   

3. Save and exit, then load the plist:

   launchctl load ~/Library/LaunchAgents/com.yourcompany.yourapp.plist
   

4. Test starting the service:

   launchctl start com.yourcompany.yourapp
   

   Check if it’s running with:

   launchctl list | grep yourapp
   

Your app will now automatically start when you boot your MacBook.

Troubleshooting Tips #

• If Apache fails to start, check the error log: sudo cat /var/log/apache2/error_log
• If your app isn’t loading via Apache, first confirm Kestrel is running by visiting http://localhost:5000 directly
• Ensure your firewall isn’t blocking port 80 (Apache) or port 5000 (Kestrel)
• Double-check file permissions for your publish folder—Apache needs read access to all files

内容的提问来源于stack exchange，提问作者Prakash Singh