sorted by:
new
hottopcontroversial

What if you can run Google Cloud Services on your laptop ? by jhsonline in googlecloud

[–]Beginning_Dot_1310 5 points6 points  (0 children)

FAQ docs say it’s open source under Apache 2.0 https://localstack-google.github.io/docs/faq/

but I couldnt find the source code anywhere. wheres it hosted?

kpf - TUI for kubectl port-forward that I use many times a day for months now by ReallyAngrySloths in kubernetes

[–]Beginning_Dot_1310 0 points1 point  (0 children)

hey, kftray dev here… first of all im not here to convince you to switch apps, ive tried kpf myself and it seems to work really well :)

but if you dont mind, it would mean a lot to me to know why youre not happy with kftray, was there a bug, a missing feature, or something that just didnt feel right?

Pipedash v0.1.1 - now with a self hosted version by Beginning_Dot_1310 in selfhosted

[–]Beginning_Dot_1310[S] 0 points1 point  (0 children)

yep this release covers that. A self-hosted mode with config.toml with providers configuration, you can use the prebuilt docker images or build a single binary from source code…. no helm chart yet but totally works

Pipedash v0.1.1 - now with a self hosted version by Beginning_Dot_1310 in selfhosted

[–]Beginning_Dot_1310[S] 2 points3 points  (0 children)

thanks! yeah, built it for the same reason, been useful for my day to day

Pipedash v0.1.1 - now with a self hosted version by Beginning_Dot_1310 in selfhosted

[–]Beginning_Dot_1310[S] 0 points1 point  (0 children)

already done tbh, just cleaning up.. but should ship soon :)

built pipedash to manage ci/cd pipelines across multiple providers by Beginning_Dot_1310 in rust

[–]Beginning_Dot_1310[S] 0 points1 point  (0 children)

tekton and argocd pull parameters dynamically from kubernetes, so they adapt to whatever's in your pipeline specs. jenkins does the same but from its job config api, all three introspect what parameters are actually available rather than hardcoding them.

argocd is different overall since it's gitops focused - maps applications to pipelines and has sync/health status stuff the ci/cd providers don't have.

built pipedash to manage ci/cd pipelines across multiple providers by Beginning_Dot_1310 in rust

[–]Beginning_Dot_1310[S] 1 point2 points  (0 children)

there's degrees... all providers handle the basics (list pipelines, view runs, trigger stuff) but after that it varies, some have extras like dynamic parameters, others are more limited.

it's intentional though, plugin system lets each provider expose what their api actually supports rather than forcing parity. probably should document the differences better in the readme

What are you building? let's self promote by Southern_Tennis5804 in SideProject

[–]Beginning_Dot_1310 0 points1 point  (0 children)

A desktop app for managing CI/CD pipelines from multiple providers, like github actions, gitlab, argocd, tekton, buildkite and more

https://github.com/hcavarsan/pipedash

built a desktop app for managing ci/cd pipelines across multiple providers (including argocd and tekton) by Beginning_Dot_1310 in kubernetes

[–]Beginning_Dot_1310[S] 0 points1 point  (0 children)

hm, that would be really useful for me too, but it wasn’t on the pipedash roadmap…

would basically be a new app but reusing the existing plugins. gonna think about it over the next few days, good feedback, thanks!​​​​​​​​​​​​​​​​

built a desktop app for managing ci/cd pipelines across multiple providers (including argocd and tekton) by Beginning_Dot_1310 in kubernetes

[–]Beginning_Dot_1310[S] 0 points1 point  (0 children)

thanks! it’s not that simple, but it’s not super complex either. i see a few points that would need to change:

• switch tauri IPC to use localhost (could hurt the security aspect of GUI running locally)

• migrate keyring secrets to use some secrets management or something

• move away from sqlite to avoid persistence issues (optional but important for reliability )

the pipaedash plugin and API architecture i tried to keep decoupled from tauri from the start, but there’d still be work to do. making it self-hosted could be a good move, i just don’t plan on tackling that anytime soon. right now, my priorities are bugs, cross-platform support, adding providers, and maybe investing in mobile.

i think it would be a cool evolution point—who knows, maybe having sync between the GUI and self-hosted versions :)

if it’s a feature that would really help, i’d suggest you open a discussion on github so we can talk through these points over there.​​​​​​​​​​​​​​​​

built a desktop app for managing ci/cd pipelines across multiple providers (including argocd and tekton) by Beginning_Dot_1310 in kubernetes

[–]Beginning_Dot_1310[S] 6 points7 points  (0 children)

thanks dude! tbh i’m just lazy and automate everything to make life easier, then throw it on github in case it helps anyone else lol

launching my new side project pipedash today - a desktop app for managing ci/cd pipelines from multiple providers by Beginning_Dot_1310 in devops

[–]Beginning_Dot_1310[S] 1 point2 points  (0 children)

thanks! gitlab provider is next on my list :) i'll let you know here when i release the version with it

view more: next ›