A command an control implementation in go. Let's see how far I can go with this.
Go to file
Stefan Friese c0764ac41d used random names to identify the agents for execution of commands, moved agentCreate step from the agent itself to the websocket server. THis means a more simple agent is possible, because it only needs to do a single request to the websocket. Cleanup needed now 2025-01-24 13:35:45 +00:00
agents used random names to identify the agents for execution of commands, moved agentCreate step from the agent itself to the websocket server. THis means a more simple agent is possible, because it only needs to do a single request to the websocket. Cleanup needed now 2025-01-24 13:35:45 +00:00
src used random names to identify the agents for execution of commands, moved agentCreate step from the agent itself to the websocket server. THis means a more simple agent is possible, because it only needs to do a single request to the websocket. Cleanup needed now 2025-01-24 13:35:45 +00:00
templates used random names to identify the agents for execution of commands, moved agentCreate step from the agent itself to the websocket server. THis means a more simple agent is possible, because it only needs to do a single request to the websocket. Cleanup needed now 2025-01-24 13:35:45 +00:00
.env added more clear output 2025-01-20 15:32:13 +00:00
.gitignore added more clear output 2025-01-20 15:32:13 +00:00
LICENSE
Makefile add autogeneration of help target for Makefile 2025-01-15 07:52:03 +01:00
README.md
go.mod used random names to identify the agents for execution of commands, moved agentCreate step from the agent itself to the websocket server. THis means a more simple agent is possible, because it only needs to do a single request to the websocket. Cleanup needed now 2025-01-24 13:35:45 +00:00
go.sum used random names to identify the agents for execution of commands, moved agentCreate step from the agent itself to the websocket server. THis means a more simple agent is possible, because it only needs to do a single request to the websocket. Cleanup needed now 2025-01-24 13:35:45 +00:00
gomatic.sql solved issue with the style of presentation of the agent response on the website. Added agentType to the api, agent and database 2025-01-22 16:02:44 +00:00
main.go used random names to identify the agents for execution of commands, moved agentCreate step from the agent itself to the websocket server. THis means a more simple agent is possible, because it only needs to do a single request to the websocket. Cleanup needed now 2025-01-24 13:35:45 +00:00
rename.sh

README.md

gontrol

A command an control implementation in go. Let's see how far I can go with this.