Add a Dashboard

[tooolbox]

Web dashboard for Dalga. Closes #22

• When you run Dalga locally, you can visit the dashboard at http://localhost:34006
• Simple HTML, CSS and JS.
• Embedded into the binary for easy deployment.
• Development mode for fast iteration (go build -tags=dev).
• Shows realtime graphs based on the /status data (5 second update window).
• Modal form for creating a new job.
• Lookup an existing job.
• Pause, resume, cancel, etc. an existing job.
• Add logo? 😉

---

One thing that I realize is missing is any kind of "listing" command for the jobs in Dalga. The dashboard can exist without it, but would be more useful if you can search through jobs and so on.

---

Another note is that I had a version of this working with Typescript and React and Material UI, with esbuild for bundling, but I decided it was entirely too complicated for the use case 😄

[cenkalti]

@tooolbox this looks really nice. I am excited!

If it's going to be easier for you, you can continue with Typescript and React and Material UI version.

For "Lookup an existing job." task, I think we also have to implement pagination for listing endpoint because the jobs table may contain many records that a client can handle. Therefore, an auto-incrementing ID field needs to be added to the jobs table if we are going to implement that feature. Or, maybe a created_at field could do the same job.

And, for the logo. "Dalga" means wave in Turkish language. We can pick up a loyalty free logo. I have found some:

• https://www.vecteezy.com/free-vector/wave-logo
• https://www.freepik.com/search?dates=any&format=search&page=1&query=wave%20logo&selection=1&sort=popular&type=vector

[tooolbox]

@tooolbox this looks really nice. I am excited!

🎉 🎉

If it's going to be easier for you, you can continue with Typescript and React and Material UI version.

Nah, it's fine, this one's farther along, and easier to iterate on anyway.

For "Lookup an existing job." task, I think we also have to implement pagination for listing endpoint because the jobs table may contain many records that a client can handle. Therefore, an auto-incrementing ID field needs to be added to the jobs table if we are going to implement that feature. Or, maybe a created_at field could do the same job.

You're totally right on the pagination! Heh, imagine if you had 10,000 jobs in there? I think the ID field/created_at is a good idea, and I am having a hard time deciding which is better:

• Created_at has more useful data within itself natively.
• If you upgraded your database by doing ALTER TABLE jobs ADD COLUMN created_at datetime NOT NULL DEFAULT CURRENT_TIMESTAMP() or whatever, all the existing jobs in your database would then have the same created_at, which makes it not very useful for pagination.

Maybe the 2nd point there is silly? Let me know what you think.

And, for the logo. "Dalga" means wave in Turkish language. We can pick up a loyalty free logo. I have found some:

Awesome, I'll look through and give some feedback :)

[cenkalti]

If you upgraded your database by doing ALTER TABLE jobs ADD COLUMN created_at datetime NOT NULL DEFAULT CURRENT_TIMESTAMP() or whatever, all the existing jobs in your database would then have the same created_at, which makes it not very useful for pagination.

Good point. Timestamp is not unique. I think it is better to use auto-incrementing integer id. If I remember correctly, MySQL generate a valid sequence of integers when adding the new column with ALTER TABLE statement.