Please note the full context of my statement: [configuring ip addresses for a web server] “…is basic I.T. stuff any I.T. tech should be able to configure.”
If someone is employed as an I.T. tech responsible for setting up and maintaining the network in an organization, they should be capable of doing this very quickly and easily. Setting up a web server is very similar to setting up various other types of servers (file servers, email servers, etc.). It’s part of their job–one of the simplest parts, in most cases (setting up security certificates and making sure the whole thing is secure is often the most involved part).
For anyone who does not manage/configure networks as part of their day-to-day job–this includes programmers, hardware technicians and even many web site designers–there are a lot of details to learn and hundreds of variations of how a network may be set up.
If you have an internal I.T. team, you should ask them the best way to set up a web server for your specific organization’s network. They might prefer an internal Linux server, internal Windows server, internal Mac server, cloud-based Linux server, cloud-based Windows server, cloud-based Mac server, running any of those things in a Virtual Machine instead of on bare metal, running alone on a machine or VM, running as one of many items on a PC or VM, running as a stand-alone app or running as a stand-alone service, running as a cgi application behind Apache (on Windows, Mac, or Linux) or IIS (on Windows) or some other web application, or numerous other possibilities…
Xojo web apps can run in ANY of those dozens of combinations of environments–and all of them require setting up IP addresses and DNS entries. I would encourage you to decide what web server approach is best for your environment, figure out how to set that up, and then you can get specific help deploying your Xojo app into that environment.
…or use Xojo Cloud to avoid most (but not all) of the complexities of setting up a web server.
For polling the clients, that’s another entirely different topic which could also be handled using dozens of different approaches in Xojo (or any other development environment). You should probably start a new topic in the forum if you want to discuss that, but just to get you started, here are a few different approaches for that:
- PC’s only talk to server when user has web site open in a browser, or
- PC’s run an agent (built with Xojo) that runs continuously (with GUI or a faceless console app or a service)
- Agents can push data to the server (server doesn’t have to know their IP addresses in advance), or
- Agents can respond when server polls them for data (data “pull” instead of “push”–but server needs list of addresses)
- Server and/or agents can search local subnet or specific IP addresses for responding service to find each other
- Server and/or agents can have a hard-coded list or a GUI-configured or file-loaded list of addresses to find each other
You could build any of those things in Xojo, or any of numerous other approaches.