What set of web technologies is suitable for a database client application?

Question

css

The question in the title is worded clumsily. I'll try to get the point across here.
So, there is a database on postgresql with business logic. There is a client application written under win32 which implements the user interface to this database.
I would like to learn how to write such client applications for the web. But there is no understanding of how technologies are related to each other, where to start, and what to limit.
That is, greatly simplifying the task, I would like to write a web client that implements something quite primitive. For example, a product directory with five fields (to have several types): name, brand from the list, visible / invisible, price, date added. In order to learn how to select / add / delete / change data from a web form. I want to share all this with rights at the database user level, that is, be able to log in from the web client. Including it will be important to determine the authorship of actions.
Well, then the mess starts in my head. In the end, I would probably like to come to node-webkit and the application on it, does this make sense? But what intermediate steps should be taken, I do not understand at all. Basic knowledge of HTML / CSS is, JS apparently has to be learned in some form. But this is only a frontend (is that what it's called right?).
Please tell me what else is missing and how it is connected with each other in the interaction scheme?

Answer 1

The easiest (to quickly start making an application) technology stack: PHP + HTML + JS (in your case, you can do without JS).
A simple, dead-end option that will be difficult to develop:
PHP connects to the database, takes the necessary data from there and generates HTML with the form. After filling out this form, the data from it is sent as a POST (or GET) request back to the PHP script, and it updates them in the database.
A better option, modular:
1) There is an RPC (remote procedure call) API (programming interface).
In simple words, a set of php files, each of which performs the necessary procedure.
Each file (php) is responsible for one operation. For example: “get IDs of records from the table for the last week”, “get records from the table by their ID”, “log in”.
2) There is an HTML file in which the data representation is stored (roughly speaking, a form into which data must be loaded)
3) There is a JS script. It communicates with the API using AJAX.
Such a system is good for its modularity. It is easy to maintain and improve.
The next level is to make a full-fledged REST API, but that's a completely different story%)

Answer 2

And 1C - unfashionable? There are downsides, of course, and you will have to set up the 1C server for postgress (it used to be that for Linux, up to 10 clients were free), but Plus, it’s easier to throw visual components on the form than in nodejs from the console
Another option is VB.NET, well, that is Visual Studio Microsoft. there you can do everything in 1s and plus a lot more