DRAFT
Opis
Task Tower is a tool for automating distributed tasks, utilizing pipelines with isolated processing steps in Docker containers, which allows users to easily scale and modify processes without impacting the entire infrastructure.
- Flexibility in task management
- Process isolation
- Increased operational efficiency
- Ease of integration and collaboration
sequenceDiagram
participant a as API
participant c as Controller
participant q as Queue
participant w1 as Worker 1
participant w2 as Worker 2
participant w3 as Worker 3
a->>c: API Call Request
c->>a: Response: Pipeline Added to Queue
c->>q: Add new task: Action1
q->>w1: Assign Action1 to Worker 1
w1->>q: Action1 Completed
q->>c: Notify Controller: Action1 Done
c->>q: Add new task: Action2
q->>w2: Assign Action2 to Worker 2
w2->>q: Action2 Completed
q->>c: Notify Controller: Action2 Done
c->>q: Add new task: Action3
q->>w3: Assign Action3 to Worker 3
w3->>q: Action3 Completed
q->>c: Notify Controller: Action3 Done
c->>q: Add new task: Action4
q->>w1: Assign Action4 to Worker 1
w1->>q: Action4 Completed
q->>c: Notify Controller: Action4 Done
The diagram shows the interactions between different participants in a task processing system. The API receives a request from a user and sends a response that the task has been added to the queue by the controller. Then, the controller adds a new task, labeled Action1, to the queue. The queue assigns this task to Worker 1, who, after completing it, informs the queue that it's done. The queue then notifies the controller that Action1 is complete. The process repeats for the next tasks, Action2 and Action3, which are assigned to Worker 2 and Worker 3, respectively. Each of these tasks is completed and reported as finished to the controller by the respective workers. Finally, Action4 is added to the queue, assigned again to Worker 1, who completes the task and reports its completion. The queue again informs the controller that the task is done.
Linux:
wget https://raw.githubusercontent.com/PiotrFerenc/mash2/main/install.sh && chmod +x install.sh && ./install.shWindows:
Invoke-WebRequest -Uri "https://raw.githubusercontent.com/PiotrFerenc/mash2/main/install.ps1" -OutFile "install.ps1"; .\install.[s1-
Linux:
wget https://raw.githubusercontent.com/PiotrFerenc/mash2/main/build.sh && chmod +x build.sh && ./build.shWindows:
Invoke-WebRequest -Uri "https://raw.githubusercontent.com/PiotrFerenc/mash2/main/build.ps1" -OutFile "build.ps1"; Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass -Force; ./build.ps1curl -X POST localhost:5000/execute -H "Content-Type: application/json" -d '{
"Parameters": {
"console.text": "hallo word"
},
"Tasks": [
{
"Sequence": 1,
"Name": "log",
"Action": "console"
}
]
}'or
echo '{
"Parameters": {
"console.text": "hallo word"
},
"Tasks": [
{
"Sequence": 1,
"Name": "log",
"Action": "console"
}
]
}' > request.json
curl -X POST localhost:5000/execute -H "Content-Type: application/json" -d @request.jsonor
C#, Go, Rust, Java, Typescript, PHP, COBOL, Erlang, Python, Ruby, Scala
Description: Clones a git repository to a local path.
Inputs:
- url (text, required): URL of the git repository to clone.
Display Name: Git Repository URL
Outputs:
- path (text, required): Local path where the repository will be cloned to.
Display Name: Destination Path
Description: Creates a commit in the git repository.
Inputs:
- path (text, required): Path to the Git repository.
Display Name: Repository Path - process (text, required): Message for the Git commit.
Display Name: Commit Message
Outputs:
- id (text, required): ID of the Git commit.
Display Name: Commit ID
Description: Creates a new branch in the git repository.
Inputs:
- repoPath (text, required): The path to the local Git repository where the new branch will be created.
Display Name: Repository Path - branchName (text, required): The name of the new branch to create in the Git repository.
Display Name: Branch Name
Description: Runs a Docker container.
Inputs:
- image (text, required): The name of the Docker image to use.
Display Name: Image Name - e (text, required): The environment variables for the Docker container.
Display Name: Environment Variables - v (text, required): Volume.
Display Name: Environment Variables
Outputs:
- id (text): The unique identifier for the Docker container.
Display Name: Container ID
Description: Appends content to a file.
Inputs:
- fileName (text, required): The name of the file to which content is being appended.
Display Name: File Name - content (text, required): The content to be appended to the file.
Display Name: Content
Outputs:
- appendFilePath (text): The path of the file to which the content will be appended.
Display Name: Append File Path
Description: Displays text in the console.
Inputs:
- text (text, required): Text to display.
Display Name:
Description: Adds two numbers.
Inputs:
- a (number, required): First number to be added.
Display Name: Number A - b (number, required): Second number to be added.
Display Name: Number B
Outputs:
- c (number): The result of addition.
Display Name: Sum
Description: Creates a file with the provided content.
Inputs:
- fileName (text, required): The name of the file.
Display Name: File Name - content (text, required): The content to be written to the file.
Display Name: File Content
Outputs:
- createdFilePath (text): The path where the new file was created.
Display Name: Created File Path
Description: Deletes a file.
Inputs:
- fileName (text, required): Name of the file to be deleted.
Display Name: File Name
- Application Programming Interface (API)
- Monitoring and Logging
- Triggering Tasks
- Handling Distributed Tasks
- Error Management
- Extensibility
- Configuration
- CLI
- prompt
- list
- run
- User Interface (UI)
- Scheduling
- Dependency Management of Tasks
- Retry Mechanisms
- Security
- Integration with External Services and Applications