Replies: 3 comments 1 reply
-
|
I am looking for feedback on this. I dont want to fork, and I think its def possible to keep Task-UI able to use docker and non docker. The runner has Supervision trees and this is why its able to run so many processes and manage their full life cycles. When I deploy to Fly.io I use runner, so I can run many processes in a single docker deploy. Aqua can be used as the binary registry, and so you can either embed your binaries on Docker or when docker boots, it can grab the binaries from the aqua registry. It's just a question of what you want. The flexibility is quite cool because you are free to run your stuff on any cloud easily OR at Edge. If I run on Edges, I just add a Caddy for protection, with a CF Tunnel. Typically I run Caddy and use Cloudflare just for the DDOS and Certs aspects which is free. |
Beta Was this translation helpful? Give feedback.
-
|
Did you try just installing and running it without docker? Pretty sure i
left a readme howto
…On Sat, Jun 15, 2024, 05:48 ged ***@***.***> wrote:
I am looking for feedback on this.
I dont want to fork, and I think its def possible to keep Task-UI able to
use docker and non docker.
The runner has Supervision trees and this is why its able to run so many
processes and manage their full life cycles.
When I deploy to Fly.io I use runner, so I can run many processes in a
single docker deploy.
Aqua can be used as the binary registry, and so you can either embed your
binaries on Docker or when docker boots, it can grab the binaries from the
aqua registry. It's just a question of what you want.
The flexibility is quite cool because you are free to run your stuff on
any cloud easily OR at Edge.
If I run on Edges, I just add a Caddy for protection, with a CF Tunnel.
Typically I run Caddy and use Cloudflare just for the DDOS and Certs
aspects which is free.
—
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABY7EEPVPBBRBA4YGKM2W3ZHO2QHAVCNFSM6AAAAABJLKU4MSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TONZZHA3DA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hey @titpetric I tried it a few weeks ago and it failed on a Mac. there is nothing , that I see , in the readme about running without docker. My intent is to get it running with Docker and Runner. |
Beta Was this translation helpful? Give feedback.
-
|
Task build and task install will build and install task-ui, using your local go installation. |
Beta Was this translation helpful? Give feedback.
-
This is the stack I use, and I am planning to make changes so that task-ui can run without docker. It needs docker a the moment.
I am using Task and Task-ui and runner.
https://github.com/titpetric/task-ui
Task-UI ONLY works with Docker and I am planning to modify it to work without Docker.
There is nothing wrong with Docker, but I find I just dont need it.
The reason I use Task is because of easy of development and where I need to have quick scripting without writing stuff with Mage or Makefile.
Its good enough for both local dev and Production !!
The Task-UI is very nice too. Its clean and simple.
https://github.com/cirello-io/runner is able to run many processes on any OS and also can run clusters of process, like when you need 3 of something for clustering. I run it locally and in Production.
It's 100% golang and just needs a ProcFile and a .ENV, so its very simple but also can do what docker and docker-compose can do.
It has a real time GUI, so I can see everything happening on all servers both locally and remotely.
Then there is aqua for package management. This is 100% goalng and works on All desktops.
It allows me to declare a binary package I need and keep it updated.
https://github.com/aquaproj/aqua
https://github.com/aquaproj/aqua-registry/tree/main/pkgs has a huge list of packages that is growing all the time.
Its 100% golang.
SO this is a good stack that can take the pain out of doing lots of development quickly with a gitops style of development without needs K8, docker and heavy stuff.
Deploy:
I can then deploy to fly.io and Cloudflare.
Runner can run things on fly.io just fine.
Beta Was this translation helpful? Give feedback.
All reactions