Hosting from the inside

Started by RoyJones, Nov 15, 2022, 12:59 AM

Previous topic - Next topic

RoyJonesTopic starter

In order to dig deeper and gain experience in administration, I want to build hosting on a localhost. At the same time, I have never used hosting myself, and the level of knowledge is no more than setting up nginx + php-fpm.
But I want to deploy a full-fledged Enterprise on the same localhost, for personal purposes, and only so that everything is configured correctly. :)

Now I have set up something like shared hosting, when one nginx, php-fpm is running, and through vsftpd virtual users manage files on their domains. The security of such a solution is a big question.

After reading the article "Hosting" on Wikipedia, I realized that I needed something bigger and fenced, because it is also necessary to set limits on resources (memory, processor, site volume), the number of domains per user, and in the future setting up mail accounts, databases and other—other-other... I want to implement all this without virtualization, ISP managers ... — everything is done exclusively by hand, in the console. The creation of new domains, users in the future to automate their own scripts.

The Internet is full of material on the topic of configuring daemons separately (nginx, postfix, *sql, openssh, iptalbes), but I could not find articles about specifically creating my own hosting so that all these daemons work together. And when, for example, users configure nginx for themselves, many people like to link a hamster to www via mount --bind, which I consider a crutch, because everything, imho, should be solved by natural indication of paths.

For example, when you make up a site on a localhost, and then upload it to Enterprise, to hosting — so I want to do the same thing, only this very hosting should be located on the localhost.
And as I study hosting from the inside, I am writing an article about it on the LOR Wiki.

I do not set myself the goal of monetization of home hosting, I just want any user to correctly configure all the necessary minimum of enterprise-level hosting.
Who to host — the user will already decide, maybe himself and friends, maybe 100900 clients, and the enterprise's capabilities rest only on iron.


I think 80% of hosting is based on ready-made solutions like virtualization tools, billing (for example, Billmanager) and control panels (ISPmanager, cPanel, DirectAdmin, etc.). Most of the software is bundled. Billing is more often self—written than a panel - because it is easier to make it.

Entirely self-written solutions are created only by monsters , and then not all, and not in everything..
That's why there are no articles — the architecture of such hosting is the intellectual property of the company.

As soon as it becomes possible to download a fully configured virtual hosting machine that can be installed on a physical server, then who wants to bother with configuring components individually?
If I wanted to open hosting NOW, I would look for an already configured virtual machine...


On hosting organization — it's enough just to read the manuals on setting up security and high performance (optimization) for the products that you are going to use — linux distribution, web server, php/perl/python, sql/ssh/ftp, selinux/firewall/nat setup.

Billing and control panel are more often either self—written or purchased (ISPmanager, Plesk, for example), depending again on the solution — if it's Win virtual, this is one thing, *nix is other virtualization and resource allocation systems.


in the company where I work, one office provides servers for rent
, just an example, they write that they have a raid, but in fact there is gmirror — what kind of raid is it — one name.

I built a web server for my client on a hardware raid without a software shame.
This is just one little thing, and there are actually a lot of them. in this regard, we are lagging behind the West. But on the other hand, there are also unique people in the West — the same Herts with their servers on home moms.
This will be a philosophical conversation to infinity, I'm trying to build a completely independent structure.