Example:

params: ONE=1 TWO=`expr 1 + ${ONE}`
steps:
  command: echo $ONE $TWO

Todo : Allow parameters other than default values to be specified when executing DAG from WebUI.

• Add API side parameter https://github.com/yohamta/dagu/blob/main/internal/admin/handlers/dag.go#L163
• Add confirmation modal on Web UI to be displayed when the start button is pressed
• Add the parameter input box to the confirmation modal

Current: bash <script> <arguments>
Should be: bash <arguments> <script>

It is still possible to call other workflows from within a workflow without problems, but it becomes confusing. Also, when a workflow is renamed, it would be inconvenient if the workflow calling that workflow is not also automatically renamed.

Desirable Functions to handle multi-level workflows:

• Ability to group and hierarchize workflows
• When the name (or location) of a dependent workflow is changed, the definition of the parent workflow is also automatically modified.

When workflows exist in multiple levels, the current status is not displayed on the top page. It would be good to have a dashboard page where the status can be checked at a glance.

I am thinking that moving to an organization repository may help to attract more contributors.

TODO

• refactor: Separate Web UI codes from go template
• refactor: Migrate Web UI codes to typescript
• feat: Add tags field to enable a workflow to have arbitrary tags (ex: - daily)
• feat: Improve Web UI design
• feat: Add the ability to update task status with a mouse click on visual graph on Web UI
• fix: Not to send mail notifications when a workflow is canceled not failed
• fix: Not to expandEnv on config page on Web UI
• feat: Add named parameters (ex: params: "p1=x p2=y")
• feat: Add stdout field that can write standard output to any file in a step definition
• feat: Add search function for workflows using free text keyword
• feat: Add sorting function to HTML tables on Web UI using react-table
• feat: start/stop buttons on Workflow list page
• feat: sorting function for dashboard timechart
• feat: filtering workflows by clicking a tag on table on Web UI
• feat: Change name field to an optional field by using the file name as a default value
• feat: Add version subcommand that shows the version (#127)
• feat: Add function to pass variables from one step to another using output field in a step definition
• feat: Add function to embed arbitrary script in a YAML file using the script field
• fix: Fix the formatting issue of scheduler's log on Web UI
• fix: Fix goreleaser config and Makefile to embed the correct version value (ex: 1.0.0) using -ldflags
• fix: Fix release GitHub Action and remove web assets from the repository (bundle.js and font files)
• docs: REST API interface

Not sure

• feat: Add No-Code GUI for workflow edit
• feat: i18n for Web UI
• test: Add tests for frontend Web UI codes in admin directory
• test: Improve the test coverage to 90%
• test: Add --race option to test command
• test: Add tests for Goroutine leaks
• feat: Add --repeat-until option to start subcommand
• refactor: Context handling logics in cmd, agent, scheduler, and unix package.
• feat: Add Until option to RepeatPolicy field to enable to specify the end time of repetitive task
• feat: Ability to manage multiple instances from a single instance on Web UI using Rest API interface
• feat: Make the agent an importable package from 3rd party software
• feat: Scheduler daemon
• feat: RBAC user authentication functionalities
• feat: Workflow layering mechanism such as JobNet
• feat: Windows support
• feat: Docker container image

From: https://dagu.pages.dev
To: https://dagu-go.github.io

I am currently testing the execution of a workflow created from the web ui, with the examples/minimal.yaml content.
From the start button I get an error "exec: no command".
From ./dagu start /home/minimal.yaml there are no errors.
Am I missing any extra configuration?
This is the content of my admin.yaml

port: 8080
dags: /home/
isBasicAuth: true
basicAuthUsername: admin
basicAuthPassword: admin

All web codes are currently written in template files.

By default, only the last 30 executions are displayed on the web, but it would be more convenient to allow retrieval of earlier execution history.

https://app.codecov.io/gh/yohamta/dagu

It would be useful to be able to pause and resume Workflow from the Web UI and commands.

continueOn:
  **failed**: true                   # Continue to the next regardless of the step failed or not
  skipped: true                  # Continue to the next regardless the preconditions are met or not

Documentation should be corrected , to change key to "failure"

It would be nice to be able to see the workflow of other instances together from a single web UI via the Rest API.

• feat: #66
• docs: build website on github.io
• fix: tests with --race
• fix: tests with Goroutine leaks
• refactor: separte the web codes from gotemplate

Not sure

• feat: scheduler function using existing cron-like go library

• refactor: parameters parsing code https://github.com/yohamta/dagu/blob/main/internal/config/config.go#L263
• feat: allow parameters that include spaces enclosed by escaped double quotes (")

This way the agent could be included in custom tools while still leveraging the UI of dagu

hello, i can not find the web ui codes, does it open source or not?
thank you.

• refactor: migrate cli library to cobra & viper in order to allow subcommand flags such as dagu server --port=8080 instead of dagu --port=8080 server
• feat: add flags for server subcommands for --port, --host, --dags

Library: https://github.com/uber-go/goleak

The package io/ioutil has been deprecated and new code is encouraged to use the respective implementations in the packages io and os.

In some cases it is a problem: e.g. When a DAG is called from other DAG and it did not run due to precondition, the result is treated as error currently. Whether precondition matched or not the result should be success.

It would be useful to create a workflow if a dry-run could be performed in the Web UI.

Libraries:

• https://github.com/go-co-op/gocron
• https://github.com/robfig/cron

Invalid history data cause the javascript crash on web UI history page.

react-dom.min.js?v=220516130708:141 TypeError: Cannot read properties of undefined (reading 'errors')
    at new Error (<anonymous>:136:22)
    at Function.createFromInputFallback (moment.min.js?v=220516130708:1)
    at moment.min.js?v=220516130708:1
    at bt (moment.min.js?v=220516130708:1)
    at xt (moment.min.js?v=220516130708:1)
    at Tt (moment.min.js?v=220516130708:1)
    at f (moment.min.js?v=220516130708:1)
    at <anonymous>:289:18
    at Array.map (<anonymous>)
    at HistTable (<anonymous>:288:12)

Something like Jenkins View allows us to filter and organize many workflows.

I started dagu with dagu server in my homedir [on Linux], and now the webui asks me to check three “errors below”. Those “errors” are — according to dagu — incompatible YAML errors, but why on Earth is dagu reading YAML files that has got nothing to do with dagu? Is it simply scanning the homedir and reading each and every YAML file it can find?

I would like to change the name dagu since it's sometimes confusing with the concept of DAG (Directed Acyclic Graph) when it is pronounced. Also, I would like to change the mascot animal, which is an animal kind, Degu, because sometimes I get confused with dagu and mistypo degu.

List of candidates (WIP):

• Autoflow
• NocodeFlow
• Flowsy
• AutoFluir
• ProsperFlow
• SimplexFlow