Application Modes
torero can run in three distinct modes for providing automation to a variety of operating environments. Each mode can be tailored to your specific scenarios, ranging from individual users to complex, distributed ecosystems.
Modes
Local Mode
Local mode is the default setting, this mode makes it perfect for users or small teams who need to run automations from a single machine. It is straightforward to use as no login is required, making it ideal for simple setups or initial testing and development phases.
Server Mode
Server mode establishes torero as a central server that does not run automations by itself but instead listens for and processes requests from connected torero clients. This mode centralizes control but delegates the execution of automations to clients. It's important to note that in server mode, the server cannot create secrets, services, or repositories directly but provides the mechanisms for clients to do so centrally.
Client Mode
Client mode is essential for managing a torero server. It connects to a torero instance running in server mode and performs all administrative tasks and automations. This mode enables the creation and management of services, repositories, secrets, and user accounts. A torero server is required for client mode to function, as all operations performed in client mode are executed against the connected server.
Feature Availability
Below is a table that provides a clear view of which features are available in each mode and highlights the dependency of server mode on client connections for running automations:
Feature | Local Mode | Server Mode | Client Mode |
---|---|---|---|
Run Automations | Yes | Via Client | Yes |
Create Secrets | Yes | Via Client | Yes |
Create Services | Yes | Via Client | Yes |
Create Repositories | Yes | Via Client | Yes |
Manage Users | No | Via Client | Yes |
Login Method | None | Via Client | Required |