What set of WEB technologies should be used for a remote equipment control project?

Question

Automation

The goal of the project is to create a Website accessible from mobile and desktop devices.
The site is hosted in the cloud.
The site presents one or two pages with buttons and sheets.
Pressing a button or selecting from a sheet sends a command to the Raspberry PI, which is behind the firewall. The
Raspberry PI receives the command and does something with it.
The question is which set of technologies to use.
-Server (PHP, Nodes.js? )
-Front-End
-Access to Raspberry PI ( websockets?)
-What hosting to use
The project is non-commercial and low-budget, traffic is low (1000 events per day), everything is done by one person with programming experience, but not on the web.
Thank you!

Answer 1

Why add a 3rd link in the form of a hosting/server?
After all, the server can be placed on the same Raspberry or, at worst, in a router ..

Answer 2

It was for security reasons in the form of hosting that I chose RasbPi. It would be possible to get by with an "iron" server (it comes out half cheaper), but there is no such protection that can be built on the RPi. Two virtual hosts:
http - for home use and
https - access to the external network.
Access via no_ip. Although I think to abandon it in April (difficulties with the provider) and made a hole through the vpn of my site. Even if someone tries to climb, without knowing the specific codes, all sorts of crap is displayed, which is of little interest to anyone. Although from the local network you can enter without a password.
Used Raspbian, Apache, MySQL, ShellInTheBox, samba, shh/sftp.
Through the use of my CMS, I am trying to implement the possibility of storing files on connected ExternalHDD (family archives) and WebDav-disks (with compression and encryption). Through ShallInTheBox such things are already being done. Also now, after switching the provider, I will organize the logging of phone calls from fritz!Box.
PS: I'm not dumping the entire RPi on the gun, but only the necessary ports through NAT: https, ssh, ShellInABox. And then, having completely different numbers than are usually assigned.

Answer 3

read here

Answer 4

IMHO
1. put on raspberry pi PHP.
2. From pages send commands via REST on raspberry pi. Here you have to open a port on the firewall for the web server. There are a lot of REST application servers in PHP.
3. Raspberry pi accepts RESTful commands and then does what you need.