Hosting a Static Php Web Page

[jfkn1ght]

Hello. I wish to use FlyEnv to host a static php web page using NGINX and expose it to the internet with port forwarding.
Port 80 has already been opened on my router. What settings and/or configuration edits do I need to achieve this?

[xpf0000]

If you have a static IP address:
• Purchase a real domain and configure its DNS records to point to your static IP address.

• Then, use this domain in FlyEnv to create your site.

If you do not have a static IP address (dynamic IP):
• You may need to use a tunneling service (e.g., Cloudflare Tunnel, Ngrok, or frp) to handle dynamic IP mapping.

• First, deploy the tunneling client on your local network or server and associate it with a public endpoint.

• Next, use the domain provided by the tunneling service or configure a custom domain (by setting a CNAME record) to point to the tunneling service’s address.

• Finally, configure this domain in FlyEnv to complete the site setup.

[jfkn1ght]

Thank you for your response!
I would like to use my computer's dynamic ip address for now, security risks aside. If possible, I also prefer not to use any tunneling service as i'm going for the most economic option. I was able to achieve this with MAMP.
I want to know if there are some lines of code I must include in the 'Configuration-Nginx' of my website?

[xpf0000]

The config file does not need to be modified.

Option 1: Using the IP Address Directly (Simple, but Limited)

• Best for: Temporary testing, access only by yourself or a few users, no requirement for a domain name.
• Steps:
  1. Run your service on the local server.
  2. Set up port forwarding on your router to direct traffic from a public port to your internal server's port.
• Access: Use your Public IP Address:Port to access the site.
• Important Notes:
  • Dynamic IP Issue: Most residential broadband services use dynamic IPs, which can change periodically (e.g., after a router reboot). You will need to check your current public IP frequently.
  • Convenience & Security: IP addresses are harder to remember than domain names, and exposing a service directly can pose security risks. Some networks may block common ports.

Option 2: Using a Domain Name + Dynamic DNS (Recommended for Dynamic IPs)

• Best for: Wanting a fixed, memorable domain name for stable, long-term access.
• Steps:
  1. Purchase a domain name.
  2. Use a Dynamic DNS (DDNS) service to solve the dynamic IP problem. The DDNS provider supplies a client (often installable on your router or local server) that frequently checks your public IP and automatically updates the provider's DNS records when it changes.
  3. Configure your domain's CNAME record to point to the DDNS provider's hostname, or use an A record that the client updates.
• Access: Use your domain name to access the service seamlessly, regardless of IP changes.
• This is the standard solution for non-static IP situations, eliminating the need for manual, frequent DNS updates.

In summary:

• For a simple, temporary solution and don't mind the IP changing: Use the IP:Port directly.
• For a stable, long-term solution with a proper name: You must use a Domain Name + Dynamic DNS (DDNS).

[ilijastanek]

Or the third option that works for me is https://pinggy.io/, pro sub is cheap and only solution that was work if your dynamic IP is behidn the NAT.

And also you can use custom domain just configre CNAME.