srevinsaju
Joined 5 years ago
Karma
17
Submissions
11
Member since
Dec 18
Recent submissions
Comment · 2 years ago
And Shadcn for Svelte: https://www.shadcn-svelte.com/
Comment · 3 years ago
Would it make sense to say Dagger is to Pulumi [1], as Terraform is to Togomak?
Comment · 3 years ago
Similar, but declarative. Dagger uses a programming language, Togomak uses a configuration language on steroids.
Comment · 3 years ago
It's also interesting that this is also a valid variable definition which does the same thing, but without the bells and whistles:
variable "name" {}Comment · 3 years ago
I shot my foot a couple of times using yaml. Thankfully, not with HCL.
Comment · 3 years ago
HCL has a JSON representation [1], internally, objects behave that way. so it should be possible to write a Jsonnet wrapper around it. Terraform can currently parse json pipelines too.
[1]: https://github.com/hashicorp/hcl/blob/main/json/spec.md
Comment · 3 years ago
One primary design goal togomak had from the beginning was concurrency. All tasks run concurrently, unless a `depends_on` argument is mentioned. `just` didn't support that when I was initially building togomak, but there is a feature coming in soon which I am looking forward to: https://github.com/casey/just/pull/1562 .
While I was building togomak, I read through Dagger [1], Earthly [2], Concourse CI [3], Jest and Make along with the stuff I was already working with - Jenkins, GitHub actions and GitLab CI. Dagger [1] is really great, I like its design - it supports writing pipelines in Python, Typescript, Go and a few more languages. togomak tries to abstract away a lot of it. Such as dependency management (in the case of python, the requirement of a python interpreter, and its package managers, etc). togomak is just a single statically-linked binary.
[1]: https://dagger.io/ [2]: https://earthly.dev/ [3]: https://concourse-ci.org/
Comment · 3 years ago
I am looking forward to a mix of both - I am hoping to add a concept called "operator" which would be a go-plugin [1], just like terraform providers, but build backends. So, someone would be able to, say, write a Slack plugin (in Go, or anything over RPC) which sends a message once a build is complete - like Jenkins/GitHub actions, or just scripts that we can reuse like GitLab CI through `modules`.
Perhaps a new registry where we can push custom modules and providers (operators in this case), I'm curious to know about if we have any existing implementations we could reuse for the registry.
Comment · 3 years ago
Yes, I have been taking a look at https://github.com/nektos/act which allows running github actions workflow locally. I am investigating if I can integrate it directly in togomak, so that users can reuse existing github action in their pipeline. For the most bit, these pipelines run in node docker containers. I'm hoping to add a concept called "operator" where you can specify or use multiple build backends like Google Cloud Build, or GitHub Actions.
Comment · 4 years ago
looks like KDE Slimbook uses bootstrap for the website :P