ok I am not proficient at reading code but this se...
# fleet
a
ok I am not proficient at reading code but this seems to indicate that the Fleet port number is hard coded, is that correct?
// Server
man.addConfigString("server.address", "0.0.0.0:8080",
"Fleet server address (host:port)")
Lines 438> from here- https://github.com/fleetdm/fleet/blob/main/server/config/config.go
m
In config.yml
Copy code
server:
  address: 127.0.0.1:443
for example
mine is bound to localhost which I’m then serving via nginx, you probably want to use your lan IP
z
@Mystery Incorporated has it right. You can set it in the config.yml as they mentioned, or you can set an environment variable
FLEET_SERVER_ADDRESS
. See https://fleetdm.com/docs/deploying/configuration for more about configuring Fleet.
It seems like there may be some confusion here... The configuration in
~/.fleet/config
is for
fleetctl
. That is the CLI client for interacting with the Fleet server. Typically you would install that on your workstation and use it to interact with Fleet.
a
ok thanks for the extra info. Please, please please please tell me where the config files for Fleet go. I have literally read that page on the config files 8 times, and I accept that this detail could be there, but I cannot find it. I know I’m verging on being rude, but I have spent hours looking for answers before making any post in here- my failure is not for lack of trying.
z
You pass the path to the config file in the
fleet serve
command (https://fleetdm.com/docs/deploying/configuration#using-a-yaml-config-file). Like
fleet serve --config /etc/fleet.yml
a
ah, that’s the missing link, thank you
z
Glad it helps!
👍 1