What is the best way to run a web server on your PC?

Question

Network administration

There is a static IP, what is the correct/optimal way to start a web server and bind domain names to this IP?
There is an Ubuntu server but it is used for the internal network. The gateway is, I will configure NAT. An image like Vagrant with a pre-configured LAMP and a Cpanel type would be optimal, but you can install everything yourself! Maybe there are some semi-finished quick solutions.
What difficulties, besides the unavailability of the server for my reason, can be when the hoster is himself, the channel width, CPU load, etc.? Thank you!

Answer 1

If you need to host something at least somewhat reliably, then this is an extremely poor choice.
A channel in a data center and a channel for a home user are completely different things. The outgoing channel from providers is usually crushed quite strongly, but you need it. In addition, if there is noticeable traffic, and it is shaped, there will be packet loss, and the brakes from the network side are even greater, respectively.
Your PC is probably not connected to the UPS, nor is your network equipment. It probably has memory without error correction, probably no raid, etc. Those. and here the reliability will not be very great, and when it is not great in several places, the probability of failure increases very quickly.
Also, you need to understand that the server must work 24/7, and it will make noise, heat up and consume electricity.
Those. it will affect comfort, and will not be free.
If you have no experience in setting up and operating a server, and judging by the question, you don’t have it, then there will be problems with reliability, security, and speed.
Vargant is virtualization, and this is an additional overhead. You will not work quickly anyway, and an extra layer is especially undesirable. Maybe it makes sense to use containers if you really need to.
In addition, you should have a good understanding of what you will have installed, how it will be installed, so that it will be clear later how to maintain it, and how to solve problems, or at least what to ask questions about. Those. installing the entire stack of individual components with reading the documentation, in the process, until I understand what I'm doing, you will only save time in the end, although it will be noticeably longer when setting up.
As a summary of your idea as a whole:
A bad channel, unreliable hardware, most likely slow hardware, unreliable power, even if you put some simple UPS - this is one side of the problem, which is about why you shouldn't do it all on your home computer. If you take into account what you need to spend in order to make at least somehow reliable payment for electricity, it becomes clear that you can rent the corresponding capacities for quite a long time, and it will be much more reliable.
The lack of configuration and administration skills is the second side of the problem, and it is about the need to immediately learn and spend time on this, or delegate this task to someone who understands. Using a blank and putting a socket is not a solution if it is not a server for internal use, to which no one can access from the outside. But you don’t want to work on a buggy slow server either ...

Answer 2

Loss of power when you are not at home
Dust, temperature
No backup
Dependence on the provider channel
This is done either by labor admins or those who are very worried about data privacy