#general

1 messages · Page 14 of 1

winter linden
#

Welcome Angie! Good to have you here, when we have a website & docs live, we’ll ping you, if you have any feedback on the copy, please share it!

Also if anyone else on the infracode team is interested in access, let us know - there are lots of terraform practitioners here and lots of interesting ideas around integrating Dagger & Terraform.

frank fossil
#

Brilliant! I'm gonna reach out to my team and send them your way! 🙂 Thanks Solomon! And rooting for you guys as you build this! 🙂

winter linden
#

Thanks 🙂

autumn swallowBOT
#

Welcome @swift barn!

winter linden
#

@urban cliff FYI @wispy tapir is working on docker run support. I’m guessing you’ll find a use to it, and can break^Wgently test it when it’s ready 🙂

urban cliff
#

I’ll be very gentle 🙂 @wispy tapir feel free to reach out if you want a crash test dummy.

wispy tapir
winter linden
#

@urban cliff are you currently stuck on this package for anything?

urban cliff
#

You mean on docker run?

winter linden
#

yes

urban cliff
#

I would love to replace my entire tf stack with it, but I’m not blocked per-se (I did start implementing docker run cue-side already btw).

urban cliff
#

It’s not usable yet but I can kick it into shape and share with you if you want

wispy tapir
#

It may be better to avoid duplicates ?

urban cliff
#

let me wrangle that stuff in shape this afternoon

urban cliff
#

@wispy tapir moving this conversation to #dev

urban cliff
# winter linden <@709546213388845056> are you currently stuck on this package for anything?

Actually, bringing back an old topic that was debated before: destroy and destroy order

Bringing up infrastructure, you may have ordered dependencies:

  • create docker network
  • create container and attach to that network

Fine so far.

Now, if “network” properties change, you actually have to rebuild the network, which means also rebuilding the container.
To do that, you have to first destroy the container.
Then destroy the network.
Then rebuild the new network, then spin the new container.

You obviously have to keep track of the state (unless your infrastructure is smart enough to reconcile random current state with desired state, which in the case of a docker host it’s not) - and even then, that only works if what you run right now is the only "thing" deploying on the target infra (an unlikely scenario).

FWIW, terraform actually does that pretty well.
I wish dagger would have this ability as well - pretty much, if something changes in the graph “call destroy in reverse order in the previous tree up to the change point, then rebuild”.

#

I can probably implement a poor man hack to work around that (storing state in labels | destroying dependent objects before rebuilding), but this will likely be quite ghetto

patent stirrup
#

@winter linden is there any way to get dagger to emit a manifest describing what was launched?

patent stirrup
#

@winter linden think reducing supply chain attacks 🙂

winter linden
winter linden
patent stirrup
#

@winter linden sure, in short what's happening is we're seeing this whole SBOM thing show up in the executive order from the white house

#

think of all the inputs that go into a system... source code, libraries, artifacts

#

metadata such as point of contact, license, for open source... location of project

#

all of this ends up in a cryptographically verifiable manifest. e.g. all the files are hashed

#

and signed

#

and all the deps too, e.g. originator signs the packages

#

so this is all static info... we could gate whether something can run based on this

#

but this is all static info

#

when it's deployed, would be good to have metadata produced which can describe what happened, signed by the thing that triggered it

#

which could be a person running a script, or some automated build process

#

and i think dagger is a good candidate for that

winter linden
#

I see, yeah makes complete sense.

patent stirrup
#

also, might be interesting to be able to include signatures of software used in the output somewhere

#

maybe not stdout/stderr... but in detailed output... basically saying deployed app-1.2.3 identified by spdx <hash> signed with <sig>

#

i'm going to be writing a lot about this in the near future

autumn swallowBOT
#

Welcome @tidal pulsar!

tidal pulsar
#

hey all! I'm Raphael. I'm here with @frank fossil and was just super curious about the project. I work on an open-source project myself, InfraCode, and am here to learn more about whats going on with dagger, as i think it might have use cases for our work!

winter linden
tidal pulsar
#

raphaelsocher

#

i need to understand the product better. ive been unable to find the documentation publicly i'm looking for

winter linden
#

That’s not surprising, the project is still private 🙂 There is some documentation in the repo but it’s still incomplete. If you take note of questions that come to mind when reading the docs, that would be super helpful so we can improve.

tidal pulsar
#

will do, tx. i'll look for access and move through it

winter linden
#

invite sent

tidal pulsar
#

very cool. thanks for the access. so at infracode we work on intermediating the infrastructure layer in simple ways for scalable design through a variety of products, built on top of hashicorp terraform. We attempt to give the new wave of ops/cloud engineers intermediate granular control levels to remove the need for deep technical competency in terraform.

we've been looking for an intermediate layer for build configuration and deployment for some of the lower level abstractions (containers, vms). dagger may fit the bill.

winter linden
#

Yes it seems like a good fit 🙂 The killer feature for you is the Cue language. You can incorporate all your config silos into the same Cue configuration - trivial to do as long as it has json/yaml compat. Then instead of writing custom one-off tools to manage your Cue config, you just define processing pipelines directly embedded inside the config - like embedding JS scripts directly inside your HTML markup.

tidal pulsar
#

yes. i've been looking deeply into packer as well. i'd be curious why you guys fit against them

winter linden
#

Your pipelines have access to the full buildkit API, so you can build and run containers at will - for example you can run terraform itself in a container, with inputs and outputs plugged into the overall Cue configuration

winter linden
tidal pulsar
#

i wish you all would handle the whole layer but too much to ask i guess 🙂

winter linden
#

There are just too many specialized tools and infrastructure to try and do it all... But gluing it all together is very useful in itself. Then it’s up to you how much intelligence you want to move into the glue itself.

tidal pulsar
#

ok. i understand. if i got this right, dagger can handle the build and deploy orchestration for machine/container/serverless deployments in a clean text based format at the application level?

winter linden
#

Buildkit is a low-level graph computation engine. You give it graphs to “solve” and it solves them. Each node in the graph is an operation: fetch this image or repository; copy this file; execute this command in a container; etc. All nodes can be executed in parallel, and all inputs and outputs between the nodes are checksummed: if an input has the same checksum from last run, it is cached.

docker build uses this to produce container images. But you can use it to execute any program that can be expressed as a graph. For example, a deployment workflow.

winter linden
tidal pulsar
#

ok awesome. thanks so much, this is super helpful. EDIT: "Declarative" ansible. very useful

winter linden
#

🙂 Yes that is a good way to put it

swift barn
#

hi all, anyone know where i can find a dagger logo of some kind? (prefer svg or png) 🙂

#

thanks

winter linden
#

We are working on a logo 🙂

winter linden
autumn swallowBOT
#

Welcome @buoyant ice!

buoyant ice
winter linden
#

Also, welcome @buoyant ice , good to have you here 🙂

buoyant ice
#

Sounds good! Glad to be here 🙂

wraith niche
autumn swallowBOT
#

Welcome @wispy hare!

autumn swallowBOT
#

Welcome @swift barn!

winter linden
#

@swift barn what’s your github account so we give you access?

swift barn
#

Hi there. I just joined by invite from @winter linden , would like to give dagger a try, as I worked on compose-ECS/cloudformation mapping, which was more complex than initialy expected 😛 Would be happy to see how Dagger addressed this chalenge

swift barn
winter linden
#

invite sent 🙂

winter linden
#

That makes me realize: we should give you all access to the example apps from the dockercon demo

swift barn
#

right, would be great!

winter linden
#

@swift barn I just gave you access to voteapp and helloapp. Everything from the dockercon talk is in there. We haven’t decided yet of a final location for those examples, so they might move in the near future.

#

If anyone else here wants to play with the example apps today, let me know and I’ll give you access. Otherwise we’ll publish it for everyone later this week.

wraith niche
#

@here Solomon is live in few minutes, showing dagger for DockerCon: https://docker.events.cube365.net/dockercon-live/2021/

Attend DockerCon 2021 to see how Docker helps make it easy for you to focus more of your time on coding the next great application: from code to cloud. Submit your registration now to attend DockerCon 2021– designed for developers by developers.

cloud canyon
#

^^^ correct link

wraith niche
drifting crown
stuck wyvern
#

Pro tip, there's a checkbox at the bottom of the that looks like you have to check it in order to proceed, you don't have to check that box 🙂

cloud canyon
#

sneaky checkboxes

loud mulch
#

lol ⚠️ night is falling very quickly in SF

drifting crown
#

great demos 👍

swift barn
#

was cool indeed, thanks

stuck wyvern
#

dagger input (no options) or something to bring up $EDITOR with configurables seems needed.

autumn swallowBOT
#

Welcome @stray void!

#

Welcome @meager stream!

#

Welcome @pseudo dagger!

#

Welcome @sacred stratus!

#

Welcome @swift barn!

#

Welcome @lucid quarry!

winter linden
#

Hi all 🙂 Make yourselves at home. Happy to answer questions

winter linden
patent stirrup
#

looks like a talk was done

#

congratulations on shipping @winter linden and team!

winter linden
#

Also for a bit later: we can also generate a web interface with custom inputs

frigid canyon
#

@winter linden my favorite part of the demo was the hello world, I feel like it really helped to understand the tight interaction you've built between cue and buildkit.

patent stirrup
#

@winter linden can i talk about dagger publicly now? 🙂

stuck wyvern
#

Demo really helps understand the applications of cue.

meager stream
#

Thanks @winter linden! And great job with the demos. It's a good thing you have a smart devops team 😉 Is the source for your demo available somewhere? I'd love to take a look, as I'm still wrapping my head around the language and how things connect

autumn swallowBOT
#

Welcome @wanton brook!

#

Welcome @restive aurora!

#

Welcome @silk apex!

silk apex
#

hello everyone

#

thank you so much for the talk @winter linden

#

was impressive !

autumn swallowBOT
#

Welcome @swift barn!

#

Welcome @frank crescent!

silk apex
#

ah ah ah it is so cool to see friendly nicknames here 😄

autumn swallowBOT
#

Welcome @hardy sparrow!

silk apex
#

ah that's better now 🙂

winter linden
silk apex
#

youhou !!!!!!!

autumn swallowBOT
#

Welcome @amber forge!

frigid canyon
#

@winter linden also re: comparison between bazel/skylark and dagger/cue, one (interesting?) way to look at it could be that skylark's focus as a language is to extend bazel (the tool), while dagger's focus as a tool is to extend cue (the language).

winter linden
patent stirrup
autumn swallowBOT
#

Welcome @vocal lark!

hardy sparrow
#

Very cool project, and I hope it brings CUE into the mainstream. However CUE is still very much in its infancy, and I could probably guess there's a mutual internal discomfort over

x: os.#Thing & {
  Arg1:
  Arg2:
}.out

right next to

y: builtinpkg.IGetFunctionSyntaxAndYouDont("haha")

Is the plan to keep dagger moving along with the same pace of development with CUE as it inevitable evolves, and potentially changes in very non backwards compatible ways?

winter linden
# hardy sparrow Very cool project, and I hope it brings CUE into the mainstream. However CUE is ...

Yes I would definitely love to get that syntactic sugar 🙂 There is an open issue for it.

One of the reasons we have made a bet on Cue, is that Marcel and the other core developers are very experienced, pragmatic and responsive. They have already shipped multiple breaking changes to the language, and so far it has always been possible to magically fix your config with cue fix. It’s quite impressive.

autumn swallowBOT
#

Welcome @oblique garden!

winter linden
#

Generally speaking, yes things break, but Cue clearly takes backwards compatibility and reliability seriously. It reminds us a lot of Python and Go in that regard. Which is not a coincidence since there is a lot of cross-pollination between the Go and Cue developers

#

The dagger repo itself is still private - if you reply with your github username, we’ll give you access right away

autumn swallowBOT
#

Welcome @strong hawk!

meager stream
winter linden
#

Done and done

winter linden
autumn swallowBOT
#

Welcome @steel ether!

autumn swallowBOT
#

Welcome @near glen!

cloud canyon
silk apex
#

@cloud canyon 404 sadly

#

private repo ?

cloud canyon
#

Yes, please share your GitHub ID and we'll give you access

silk apex
#

@cloud canyon @silk apex <--- my github ID

#

thanks a million

cloud canyon
#

Invite sent!

silk apex
#

awesome

restive aurora
#

@cloud canyon I would like to test it too, can I have access? ( neoandroid on github)

winter linden
#

We now have a docs site 🙂 Not a lot of content yet, but we’ll push an update next week

restive aurora
#

great, thanks!

silk apex
#

Awesome @winter linden

autumn swallowBOT
#

Welcome @abstract grove!

abstract grove
#

@cloud canyon go on, give me access - SvenDowideit as always 🙂

#

@winter linden congrats on yet another excellent timing to fill a need

cloud canyon
#

Hey @abstract grove! Good to see you 🙂 Invite sent

abstract grove
#

merci 🙂

serene thistleBOT
autumn swallowBOT
#

Welcome @hexed summit!

winter linden
#

This is turning into a Docker reunion 😁

#

Welcome @abstract grove @hexed summit 🙂

abstract grove
#

grin

hexed summit
#

👋

#

Have been very curious what you've been working on Solomon

#

And Andrea. Reunion indeed!

autumn swallowBOT
#

Welcome @raw spruce!

silk apex
#

oh !!! friendly faces !!!! @hexed summit @abstract grove 🙂

#

been wondering how to compare dagger with waypoint from hashicorp ?

#

quoting:


Waypoint uses a single configuration file and common workflow to manage and observe deployments across platforms such as Kubernetes, Nomad, EC2, Google Cloud Run, and more.```
autumn swallowBOT
#

Welcome @distant dome!

wraith niche
#

Cue is more powerful, which allows dagger to express everything in Cue, not just the declaring a deployment plan, but also the implementing of the underlying packages as well. (Waypoints requires HCL on one side and Go for the underlying dependencies, similar to Terraform in a way).

#

by the way, if anyone here has experience using waypoint (even if it's just a hello-world), I am curious to read some feedback

silk apex
#

@wraith niche we had a talk and demo about waypoint that I could share

wraith niche
#

For anyone who installed dagger v0.1.0-alpha.7 in the last 14 hours. The version check was broken, so you'll have to force-install v0.1.0-alpha.8 in order to be notified for newer versions again. Here is how to do so: https://docs.dagger.io/devel/install

Dagger Docs

Dagger Documentation

autumn swallowBOT
#

Welcome @swift barn!

autumn swallowBOT
#

Welcome @swift barn!

swift barn
#

just seen the recording of the dockercon session, amazing! Registered for early access, any way to get my hands on that soon? 😄

wraith niche
swift barn
#

thanks @wraith niche it's andreaturli

wraith niche
swift barn
#

awesome!

wraith niche
#

please share your feedback, good or bad! the project is still moving a lot and the feedback is super useful

swift barn
#

I can see homebrew-tap and examples projects at https://github.com/dagger is it correct? @wraith niche

GitHub

dagger has 2 repositories available. Follow their code on GitHub.

swift barn
#

ah no scratch that your invitation is just arrived. all good! thanks

swift barn
#

trying to follow https://docs.dagger.io/devel/programming

❯ dagger up
5:14PM INF system | starting buildkit    version=v0.8.3
5:14PM INF repo | computing
5:14PM INF repo | #4 0.021 Initialized empty Git repository in /var/lib/buildkit/runc-overlayfs/snapshots/snapshots/5/fs/
5:14PM ERR repo | #4 0.259 fatal: could not read Username for 'https://github.com': terminal prompts disabled
5:14PM ERR repo | failed: rpc error: code = Unknown desc = failed to load cache key: failed to fetch remote https://github.com/dagger/dagger: exit status 128    duration=300ms
5:14PM FTL system | failed to up environment: buildkit solve: task failed: failed to load cache key: failed to fetch remote https://github.com/dagger/dagger: exit status 128
#

what are the requirements on the git repo?

winter linden
#

What commands did you run?

swift barn
#

dagger init in a new empty folder, dagger new staging and created a staging.cue under .dagger/env/staging/plan/staging.cue

#

and finally dagger up

#

I'm using docker on mac 3.3.3

winter linden
#

yeah that should work. Can you show the contents of staging.cue ?

#

it looks like it’s trying to pull from a private repo, and failing to prompt you for credentials

swift barn
#

sure

package main

import (
    "dagger.io/docker"
    "dagger.io/git"
)

// Relay for fetching a git repository
repo: git.#Repository & {
    remote: "https://github.com/dagger/dagger"
    ref: "main"
}

// Relay for building a docker image
ctr: docker.#Build & {
    source: repo
}
#

I believe there's something wrong with my ~/.gitconfig

winter linden
#

Just to confirm that git auth is the problem, can you try with a public repo?

sacred stratus
#

👋 super cool session.. got me more interested in automation :D.. would be cool to get access to be able to check it out more.. my github account is stoffeastrom

swift barn
# winter linden Just to confirm that git auth is the problem, can you try with a public repo?

changed to

package main

import (
    "dagger.io/docker"
    "dagger.io/git"
)

// Relay for fetching a git repository
repo: git.#Repository & {
    remote: "https://github.com/dagger/examples"
    ref: "main"
}

// Relay for building a docker image
ctr: docker.#Build & {
    source: repo
}

different error

❯ dagger up
7:57PM INF repo | computing
7:57PM INF repo | completed    duration=400ms
7:57PM INF ctr | computing
7:57PM INF repo | #4 0.344 5dc7ad56c5ac2d89dff718b73c92efc948c146f5    refs/heads/main
7:57PM ERR ctr | failed: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to read dockerfile: open /tmp/buildkit-mount260614179/Dockerfile: no such file or directory    duration=300ms
7:57PM FTL system | failed to up environment: buildkit solve: task failed: failed to solve with frontend dockerfile.v0: failed to read dockerfile: open /tmp/buildkit-mount260614179/Dockerfile: no such file or directory
#

so I think this confirms it's git auth?

winter linden
#

Yes

#

@cloud canyon any tips on private git repo auth? ☝️

sacred stratus
#

🤔 I would try either with ssh url (don't know if that's supported) or maybe create a personal access token to be used in the url.. Just thinking out loud here 🙂

cloud canyon
cloud canyon
silk apex
#

stupid question, but where to find the source code of dagger/aws ?

#

clearly not a cue guru but willing to see how hard it could to be to build an Azure module

cloud canyon
winter linden
#

Hi @everyone, we need your help! Before we can launch, we need a great tutorial, to make it as easy as possible to learn the basics and get up and running with Dagger. We are working on prototypes. But we are still searching for the right format and content. There are so many possible ways to get started, since there are so many different things you can do with Dagger. That’s the problem with open-ended platforms…

If you have ideas or suggestions for a great tutorial, we are interested! How would YOU like to learn Dagger?

frank crescent
#

My take is to map it to LEGO sized edibles. A simple frontend, a simple backend. Then marry those to a “stack” with a frontend and a couple of backends. Slow, methodical.

#

I’m also a barbecue guy from Texas, so maybe that’s how I view everything: small things coming together to make a grander collective

swift barn
#

perhaps a katcoda of the voting app dagger example?

serene thistleBOT
#

I find the dagger input commands a bit cumbersome, there's a lot to type and somehow I always type the wrong thing.

What are your thoughts about using flags rather than sub-commands to set the different input types? The obvious downside is "flag mess", but I don't know if that's worse than what we have now.

Examples:

Regular text input (default)

dagger set foo bar

git

dagger set repository --git https://github.com/dagger/dagger.git --git-ref main

OR

dagger...
winter linden
#

Good suggestions @frank crescent @swift barn . We are starting from the apps from the dockercon demo. A few open questions:

  • Should the first tutorial require credentials to eg. AWS? More realistic but also more friction.

  • Should we prioritize simplicity (“run a container that say hello world”) or realism (“do something useful with this docker-compose project”)

  • If we want 1) realism and 2) no infra credentials required, then what realistic thing can we do?

  • Is it better to have one big tutorial (possibly with many chapters) or a menu of mini-tutorials focused on specific use cases (and if the latter: which useccases?)

frank crescent
#

I’d say keep it generic. Plain K8s. Anyone can run it on real clusters, kind, or minicube.

abstract grove
#

that's a great point - I'm going in a very different direction, as I actually need a workflow system - so I'm not that interested in k8s, or even trad push to cloud

#

focusing the initial tutorial set to "so you already have a k8s" means you can avoid the friction of creds

#

even so, what I'm desiring most, is strong reference docs for stdlib, which includes working examples for each bit

abstract grove
#

yeah, but its kinda more generic than each cloud - especially mixing in the cloud infra someone like me uses (edu on prem, and edu country prem)

#

plus all the HPC weirds

winter linden
#

A lot of (potential) dagger users don’t use kubernetes. It’s not trivial to assume everyone does, especially in the very first tutorial

#

of course we want a kub tutorial but maybe not in dagger 101.

abstract grove
#

oh, very true - k8s is almost irrelevant for my current thing - I'm thinking more like airflow

frank crescent
#

Fair point, but I’d think K8s is as close to the “meaty middle” as you can get at the moment

#

Happy to be proven wrong. My spouse does it all the time 😄

cloud canyon
#

maybe a tutorial with a static frontend (s3 or netlify) plus a tutorial with a container on k8s could be a good start

it should sound familiar to both the frontend and the backend crowds

#

if not familiar, at least not alien 🙂

abstract grove
#

oh - big q @winter linden are you thinking new users need to read the cuelang docs after 101, or are you expecting to delay that to the point where the dagger user is almost expert

#

cos that hit me pretty quickly yesterday (and yes, i ack that i have an unusual learning pattern)

winter linden
#

Good question. One more for the list 🙂

abstract grove
#

but $dayjob is also pushing things around, so \o/

autumn swallowBOT
#

Welcome @dense mural!

torpid linden
swift barn
autumn swallowBOT
#

Welcome @tired furnace!

autumn swallowBOT
#

Welcome @swift barn!

#

Welcome @granite dust!

near glen
#

may I get access to the dagger repo? My GH username: corntoole

swift barn
#

how can I get a more verbose dagger up ?

cloud canyon
#

@swift barn with -l debug

swift barn
#

I'm not entirely sure I understand the workflow here, for examples like simple-s3 do I need to make sure that the infra required is already there, maybe using tf or something similar? or dagger is supposed to provision it for me, assuming the cue is able to do that?

wraith niche
#

You can change it either from the cue code or from an input string from the cli.

#

I can add some config to provision the bucket if it does not exist. Would it be helpful?

swift barn
wraith niche
#

Of the config or dagger?

swift barn
#

dagger s3 module, I think. I can see some usecases where I can accept get_or_create bucket before the deployment.
For sure, if I have already invested on tf or alike, I may want to reuse it, but if I have to start from scratch I'd prefer to use a single tool, at least personally

#

totally fine, if you guys think otherwise, just trying to give first impressions on the tool, if helpful, and learn from the discussion

wraith niche
autumn swallowBOT
#

Welcome @rocky flame!

rocky flame
#

Hello Dagger team 👋 I am Romaric, CEO and co-founder of Qovery. I can't wait to see how Dagger works 🙂

swift barn
winter linden
#

@swift barn dagger can provision your infra. The s3 package at the moment doesn’t support it, but could (and should) in the future. It may wrap terraform or pulumi to do so, or call s3 api directly - up to the package implementation.

winter linden
#

For example in early dagger prototypes we implemented a complete Jamstack setup on AWS & Netlify, from scratch. It can auto-provision an ECS cluster with all required resources (vpc, elb) as well as an RDS instance. In this case the provisioning is done with Cloudformation, via the package dagger.io/aws/cloudformation

#

Hi @rocky flame 🙂 Welcome

rocky flame
#

Hey @winter linden - happy to see you here. If you accept me in the beta I'd love to give you some feedback and why not writing an article - happy to give a try to Dagger

winter linden
rocky flame
winter linden
#

invite sent

rocky flame
#

Done, I am digging into the project to see how it works and give it a try this week

autumn swallowBOT
#

Welcome @grand pilot!

#

Welcome @gentle flicker!

rocky flame
#

Hey @grand pilot @gentle flicker 👋

#

Hey @drifting crown ^^ I recognize your avatar

grand pilot
#

Hey 👋

tired furnace
#

Hi there ! Curious about Dagger, I can't wait to give it a try 🤓 . I've requested an early access from the dagger.io front page, but have not been accepted yet. So I'm lurking around in the meantime 👀 .

silk apex
#

Oh hey @tired furnace

#

Stop lurking and start contributing 😉

tired furnace
#

Hey @silk apex 👋 Looks like there's a strong French community here ! 😁
I'm happy to contribute my small part (local community talks, documentation feedback, examples...) when I can get my hands dirty ! I guess if I get my early access request gets accepted I'll have access to github, so I can start playing with it ! 🤞

silk apex
#

You'll definitely love it

gentle flicker
#

Hello there

wraith niche
#

Hello @rocky flame, @tired furnace and @gentle flicker, Welcome!

#

@tired furnace give your github nickname, I'll give you access now

sacred stratus
#

@wraith niche Hi, could I also get github access :D. gh stoffeastrom

tired furnace
#

@wraith niche Great! My github is hervenicol . Thanks!

rocky flame
#

Hey @wraith niche nice to meet you

wraith niche
autumn swallowBOT
#

Welcome @severe coral!

severe coral
#

👋

winter linden
#

Glad you could make it @severe coral 🙂

autumn swallowBOT
#

Welcome @swift barn!

#

Welcome @rain oriole!

autumn swallowBOT
#

Welcome @coral elm!

#

Welcome @magic rivet!

wanton brook
#

Hey all! Exciting work happening here. I'd love to get an invite 🙂 GitHub username: edvald

cloud canyon
#

@wanton brook Welcome! Invite sent

serene thistleBOT
autumn swallowBOT
#

Welcome @coarse agate!

coarse agate
#

👋

swift barn
#

welcome @coarse agate !

swift barn
wraith niche
#

v0.1.0-alpha.10 is out 🔥

Major changes:

🔑 Secrets Support

  • Encryption at rest (using mozilla/sops and FiloSottile/age)
  • Encryption in the Cue tree (e.g. dagger query will not / cannot show plaintext secrets)
  • Leverages BuildKit Secrets: dagger.#Secrets are in-memory mounted in containers, will not end up in image layers / cache
  • Secrets are automatically redacted from console logs, in case you print them by mistake

🔎 Output listing
dagger output list can now display the list of outputs of an environment (e.g. URL), opposite to dagger input list

✏️ dagger input edit
Bulk edit all the inputs from your favorite $EDITOR

🐳 docker.#Run support
Run docker containers on remote hosts using ssh

and a bunch of other fixes/enhancements: https://github.com/dagger/dagger/releases/tag/v0.1.0-alpha.10

Install/upgrade instructions: https://docs.dagger.io/v0.1.0-alpha.10/install

Dagger Docs

Dagger Documentation

serene thistleBOT
serene thistleBOT
#

I agree that the current UI for inputs needs improvement.

A few questions and comments:

*dagger set instead of dagger input

OK with me.

dagger input unset would just become dagger unset

Makes perfect sense.

[Use flags instead of sub-commands]

I don’t hate it, but it doesn’t solve the “lots to type” problem. All commands are the same length or longer, except for the special case dagger set foo bar. It feels more like a subjective preference to switch to...

timid quiver
#

Just noticed Docusaurus specific PRs? Are we using v2?

#

I have been spending almost 2-4 hour daily with Docusaurus and keen to know how is it being leveraged here?

winter linden
#

That is a question for @last pine 🙂

last pine
timid quiver
#

Cool @last pine

#

Are we planning to host the complete documentation in Docu

#

I found google/docsy quite simpler than facebook/docu v2 though

last pine
#

probably. We were thinking using either docusaurus or Vuepress

#

I never used google/docsy

timid quiver
#

Never used Vuepress. Will look into it

last pine
#

I'm looking how Docsy works

timid quiver
#

Docsy is Hugo-based, quite easy to use.

frank crescent
#

I can also +1 Hugo and Docsy. Really like that it can implement self-hosted search, too. No server-side components needed.

#

Would love to take a peek at the current state. GitHub ID: cjchand

stable mulch
#

https://getdoks.org/
I have no experience with doks, but looks fine. https://litestream.io site uses it. (https://news.ycombinator.com/item?id=26106644)

Doks

Doks is a Hugo theme helping you build modern documentation websites that are secure, fast, and SEO-ready — by default.

camkego

Ben, this is impressive work, and I will almost certainly use it. (Already believe in sqlite vs mysql/PG/Redis) But as a backend developer I am always trying to learn simpleR ways to build beautiful open source websites. Would you mind sharing how you built the site? I see Bootstrap. Would you share the tools you use? Thank you, Cameron

Litestream is an open-source, real-time streaming replication tool that lets you safely run SQLite applications on a single node.

frank crescent
autumn swallowBOT
#

Welcome @stuck jacinth!

autumn swallowBOT
#

Welcome @swift barn!

autumn swallowBOT
#

Welcome @hallow atlas!

hallow atlas
#

Hello everybody (from France), I just been invited by my friend and mentor, @swift barn

swift barn
#

your MY mentor dude (p.s let them know your github id) 🙂 my french is so bad i needed to call in reinforcements @winter linden 🙂

hallow atlas
swift barn
severe coral
#

Hello @hallow atlas

winter linden
#

Reminder to everyone, there is also https://docs.dagger.io although there is a lot of missing content. We are working on a more complete version.

autumn swallowBOT
#

Welcome @unreal lion!

unreal lion
#

Hi all, I think I know a few of you in here! I'm looking forward to playing with Dagger, the demo was pretty compelling

winter linden
#

Welcome @unreal lion 🙂

swift barn
#

Welcome @unreal lion

autumn swallowBOT
#

Welcome @steel valve!

patent stirrup
#

@winter linden is the video available on YouTube?

winter linden
#

Good question, It doesn’t look like it but I’ll ask the Dockercon crew

autumn swallowBOT
#

Welcome @keen yew!

sly spade
#

Hi dagger community! Delighted to be here and would love access to the repo to play with the product (@sly spadekhaliq)

wraith niche
sly spade
autumn swallowBOT
#

Welcome @violet tapir!

autumn swallowBOT
#

Welcome @modern badge!

modern badge
#

Hi there! I'd love to get early access to Dagger repository. GitHub ID: juliengric.

wraith niche
steel valve
winter linden
#

Thanks 🙂 I just posted as well in support of Cue. My first hacker news post in years!

steel valve
silk apex
#

gosh ! following the progress on the tool , making me loving it more and more each day

winter linden
#

@everyone any volunteers for testing our (still work in progress) tutorial for getting started with Dagger? We’ll release later this week and start inviting people from the waiting list

silk apex
#

@winter linden will do definitely!

winter linden
#

Please take notes as you go, if you can! The more detailed the better. Especially things you didn’t understand, commands that didn’t work on the first try, etc. Anything that goes through your head as you follow the tutorials is useful.

timid quiver
#

@winter linden 🙌 Keen to test it. Will go through the tutorials.

winter linden
#

Thanks @timid quiver !

#

In case you’re starting right this second, please give it another 15mn, we are about to merge a few last minute changes

torpid linden
#

This might not necessarily be relevant for Dagger. It seems that I needed something to allow me to combine and process config files. Cue itself might be enough for things that don't need to be deployed somewhere. Perhaps dagger would also work for this particular use case. Please let me know if this is a better topic for #help-old-do-not-post.

winter linden
# torpid linden This might not necessarily be relevant for Dagger. It seems that I needed someth...

I think Dagger can potentially help, for example if you want to formalize your config processing pipeline end-to-end: where to fetch files and directories; where to upload the results; what tools to execute along the way, etc

If you can share more details about your use case, I can try to give you a more helpful opinion 🙂

Either way it’s easy to switch from pure cue to Dagger+cue, and vice versa.

torpid linden
#

@winter linden: It's just a bunch of files which build a config right now. I could contribute that as a PR to the docs once it's ready to show to others. Dagger+cue seem to be the right tool for the job though. The only concern I have with dagger is that I may want to avoid running something in containers (if it just processes some config files). This is one of the reasons I've brought this up - to make sure this is also one of the use cases.

winter linden
#

It talks about the “software BOM” requirement

winter linden
#

Thank you @near glen @coarse hatch @urban cliff @mint axle for your detailed feedback on the tutorials! We’ll incorporate as much of it as possible today.

autumn swallowBOT
#

Welcome @warped jay!

autumn swallowBOT
#

Welcome @elder oar!

#

Welcome @elfin scaffold!

elfin scaffold
#

Hello!

#

Excited to start playing around with Dagger 🗡️

winter linden
elfin scaffold
#

@winter linden saw your talk at DockerCon, was super excited to see Cue-lang under the hood

winter linden
#

The docs & tutorials are brand new so please let us know if you find anything confusing or broken… We will keep improving 🙂

autumn swallowBOT
#

Welcome @solid lion!

#

Welcome @worldly ravine!

elfin scaffold
#

What's a good channel to inquire about bugs/etc?

winter linden
#

Still a pretty small group so it’s not too noisy 🙂

elfin scaffold
winter linden
#

Might be an error in the tutorial app itself… We will investigate. Sorry

#

Did you see any errors during dagger up?

cloud canyon
#

doesn't seem to be deployed

elfin scaffold
#

Just a few warnings

#

No indication of a fatal error

cloud canyon
#

weird, I don't see s3 in the logs

winter linden
#

I don’t see any upload in the logs?

cloud canyon
#

@elfin scaffold any errors at the top?

elfin scaffold
#

line above the output is dagger up

winter linden
#

can you try dagger up -l debug ?

elfin scaffold
#

sure

cloud canyon
#

@wraith niche ^^^

autumn swallowBOT
#

Welcome @fiery ore!

elfin scaffold
#

@winter linden debug output ^

cloud canyon
#

Found the error 🙂 Pushing a fix in the example, sorry about that!

#

[double checking things, please hold a sec 🙂 ]

patent stirrup
#

@winter linden i'm involved

#

in fact, they are using one of my projects to test SBOM tooling and format compatibility for go projects

cloud canyon
#

@elfin scaffold it's fixed 🙂 you just need to git pull the examples, sorry!

elfin scaffold
#

Thanks @cloud canyon and Team

patent stirrup
#

i really need to start blogging :x

autumn swallowBOT
#

Welcome @fresh zephyr!

fresh zephyr
#

Hello world!

#

Dagger vs. artisanal deploy scripts
I feel personally attacked by this

winter linden
#

Ha ha 🙂 We all have those.

fresh zephyr
#

In the vs. page would it make sense to also compare it to ansible or similar (chef, puppet, salt, fabric)? I'm still fully trying to understand what all dagger can do.

winter linden
#

Yes it would make sense

patent stirrup
#

@winter linden check your PM when you get a chance, looking for some feedback that is time sensitive. 🙂

#

NTIA SBOM feedback is due today, want to make sure what i wrote makes sense. :x

#

or if i am missing anything

winter linden
#

Will check, sorry no time to review today (past midnight here)

patent stirrup
#

ah no worries

#

it'll all become public record regardless, and i'm involved in the working sessions that will continue after the inputs are aggregated

#

in short, feedback is still useful even after the fact

fresh zephyr
#

@patent stirrup , if you don't mind the random person, I wouldn't mind looking at the SBOM document. I work in the software supply chain security industry, though unfortunately before any of the good standards came out like SPDX or Cyclone. We generated our own SBOM format that I'm not fond of but we are locked into now.

modern badge
#

The authorization scope needs some tweaking. I'm reluctant to give the Dagger Docs application full access to my account information and I'm guessing others may as well.

patent stirrup
#

@fresh zephyr sending a PM

winter linden
last pine
last pine
autumn swallowBOT
#

Welcome @fiery flare!

cloud canyon
#

Hey @modern badge -- @last pine pushed a fix and we just deployed it. Thanks for the feedback

autumn swallowBOT
#

Welcome @swift barn!

autumn swallowBOT
#

Welcome @zenith plume!

winter linden
#

Welcome @zenith plume ! Glad you could make it 🙂

zenith plume
autumn swallowBOT
#

Welcome @somber ore!

autumn swallowBOT
#

Welcome @indigo hamlet!

winter linden
autumn swallowBOT
#

Welcome @signal tulip!

#

Welcome @swift barn!

#

Welcome @swift barn!

autumn swallowBOT
#

Welcome @pliant gazelle!

autumn swallowBOT
#

Welcome @swift barn!

swift barn
wraith niche
#

To anyone who played with Dagger, following the docs: we're looking for feedback, especially the bad one. If you have some time to spare, would love to ask some questions: https://calendly.com/samalba - we can also spend this time to talk about your use case.

autumn swallowBOT
#

Welcome @zealous creek!

#

Welcome @dire nacelle!

autumn swallowBOT
#

Welcome @stray jolt!

stray jolt
#

👋 excited to be here!

winter linden
#

Welcome 🙂

#

Looking forward to getting buried in feedback 😉

stray jolt
#

@winter linden got your back, also would love to show you what we're doing!

silk apex
#

@wraith niche will play with the getting started in the next few hours, i'll do my best to write down some feedbacks 🙏

wraith niche
autumn swallowBOT
#

Welcome @swift barn!

silk apex
#

@wraith niche should i create an issue for each improvements i've seen ?

wraith niche
winter linden
#

You can’t go wrong with a github issue or github discussion @silk apex 🙂

silk apex
#

ah ah @winter linden 😄

#

let's open issues and then happy to PR if topic agreed @wraith niche

silk apex
#

opened few issues, my main point @wraith niche is the getting started isn't suited at this stage for newcomers, needs a bit of tweaks here and there

silk apex
#

happy to help anytime @wraith niche

autumn swallowBOT
#

Welcome @candid crag!

silk apex
#

@hallow atlas not sure tbh

autumn swallowBOT
#

Welcome @uneven stump!

#

Welcome @echo rover!

autumn swallowBOT
#

Welcome @spring bough!

autumn swallowBOT
#

Welcome @swift barn!

#

Welcome @swift barn!

autumn swallowBOT
#

Welcome @gentle lark!

#

Welcome @cerulean wraith!

winter linden
#

Welcome everyone 🙂

autumn swallowBOT
#

Welcome @undone bloom!

autumn swallowBOT
#

Welcome @wary pumice!

#

Welcome @ivory compass!

autumn swallowBOT
#

Welcome @median arch!

autumn swallowBOT
#

Welcome @noble fjord!

noble fjord
#

you had me at "alternative to scripts" .. let's play 🙂

cerulean wraith
#

hey everyone, thanks for inviting me to the community here. i am trying to deploy my vuejs based app on netlify

#

i setup my inputs as dagger input text site.netlify.name <name> and similarly for site.netlify.account.token

#

also did the input for src using dagger input dir src ./

#

now when I run dagger up, i get errors

#

import (
    "dagger.io/netlify"
)


// Netlify site
site: "netlify": netlify.#Site & {
    contents: app.build
}
#

and the source is ```package multibucket

import (
"dagger.io/dagger"
)

// Source code of the sample application
src: dagger.#Artifact & dagger.#Input```

autumn swallowBOT
#

Welcome @swift barn!

#

Welcome @twilit pendant!

twilit pendant
#

thrilled to be here 👋

winter linden
cerulean wraith
#

but the experience looks really slick !!

winter linden
#

Ok great! Which tutorial is that? 102?

#

@cerulean wraith any feedback you have on how to improve the experience, please let us know!

#

thanks for testing!

cerulean wraith
#

sure thing, my pleasure

#

can I submit PR for tutorial?

winter linden
#

absolutely! pr, issue, discussion thread, whatever works best

cerulean wraith
#

gr8, thanks

winter linden
#

Heads up everyone, we are making a breaking change in this new release. All “dagger universe” packages must be imported from alpha.dagger.io instead of dagger.io previously.

For example, if your code has this import:

import (
  “dagger.io/os”
  “dagger.io/netlify”
)

After upgrading, you will need to change it to:

import (
  “alpha.dagger.io/os”
  “alpha.dagger.io/netlify”
)

We are making this breaking change now before ramping up the number of invited testers, to minimize the pain.

The goal of this change is to make it more clear in your code how mature your dependencies are. This is inspired by a similar system in Kubernetes resource naming system, and feedback from some of you (thanks!)

autumn swallowBOT
#

Welcome @frozen socket!

frozen socket
#

hi everyone! 👋
I haven't got my hands dirty yet but just wanted to let you know that the Discord invite link in the welcome email is broken (I used the one from docs.dagger.io)
Looking forward to see the possibilities of Dagger!

cloud canyon
#

hi @frozen socket, welcome! Thanks for letting us know, will look into it right now

#

Fixed 🙂

autumn swallowBOT
#

Welcome @sharp estuary!

#

Welcome @topaz elm!

autumn swallowBOT
#

Welcome @sly palm!

autumn swallowBOT
#

Welcome @hoary spoke!

hoary spoke
#

Hi everyone! Dagger is amazing ❤️

winter linden
#

Thanks @hoary spoke 🙂 Were you able to complete the tutorials? Anything we can do to improve the experience?

cerulean wraith
#

can we use multiple age keys for different projects in dagger

winter linden
#

If you have a preference in user experience or implementation, now is the time to share it !

cerulean wraith
#

i am planning to move all my personal projects over to dagger over this weekend (i do manual installations today beside netlify)

#

hopefully you have left room for some feedback there 😉

cloud canyon
#

yes please 🙂

hoary spoke
cloud canyon
sly palm
#

I also started going through Docs and tutorials, looking forward to contribute in this amazing tool.☺️

cloud canyon
#

@winter linden background: @wispy tapir is adding tests in sub-packages within universe, however sanity-check breaks as it doesn't like sub-packages

winter linden
#

Ah. Sorry 😉

#

how can I help? 724 looks good to me. Do you need extra help fixing that test?

cloud canyon
#

@winter linden since there's a cue.mod in universe now, "cue eval alpha.dagger.io/alpine" works out of the box, no need to vendor stuff, so I tweaked the test not to vendor anymore, fixed the test apparently

winter linden
#

nice. So you don’t need to mount universe packages to a cue.mod/pkg, thanks to the module name in module.cue?

#

I love it. I actually started with a single “context” field too and mounted universe directly, but it broke imports. I added the vendor map as a solution, but didn’t think of just adding a module.cue

autumn swallowBOT
#

Welcome @swift barn!

cerulean wraith
#

is it possible to push docker images to github container registry?

winter linden
#

Ah, yes but it might require writing a little glue for authentication, like we did for ecr & gcr

cerulean wraith
#

yes, reading that code now to see how that might work

winter linden
winter linden
#

@cerulean wraith if you want, we could do a coding session together next week on this, maybe others here would like to join. What is your timezone & most convenient times in the week for spending time on dagger?

cerulean wraith
autumn swallowBOT
#

Welcome @rain hare!

autumn swallowBOT
#

Welcome @barren sparrow!

barren sparrow
#

Aloha! 🙂

last pine
#

welcome @barren sparrow

autumn swallowBOT
#

Welcome @smoky shard!

winter linden
severe coral
#

So I am up for adding docs section for civo Kubernetes also Up for adding the key step so that people do not miss adding key from 101 section.
Few questions or maybe feedback,

  • can I use any language code and then build and deploy using dagger to Kubernetes?
  • for Infra, people would use terraform to spin up and then Dagger is there for applications build and deploy,
  • since its CUE magic that you can use(which I have to learn of course) Or @winter linden can teach live on a stream with me 😉 but how can I use my custom app to deploy to Kubernetes using Dagger directly from source , I can try and along the way note down the steps maybe?
  • also the key is there for sample app but how can we use our own key?
autumn swallowBOT
#

Welcome @eager dune!

cloud canyon
severe coral
cloud canyon
cloud canyon
#
  • also the key is there for sample app but how can we use our own key?

Short answer: you have nothing to do, when you dagger new it will be using your own key

Long answer: ~/.config/dagger/keys.txt contains your keys (it's a keychain)

You should have 2 keys in there: The first one is your own key, the second one is the sample app key

When you dagger new it will use the first (your own) key.

The other keys in the file grant you access to already existing environments, the first key is the only one used in dagger new

(UX will be simplified soon)

#

@severe coral let me know if that was clear enough, happy to help, and thanks for the feedback!

severe coral
# cloud canyon <@!710457512389902396> let me know if that was clear enough, happy to help, and ...

Thanks for the answers,
Yes I have a stream in sometime, after that will be back on Dagger on few other stuff, I think We should have a FAQ section as well and I can help that shaping that up, will write in a doc few common questions and then we can keep on adding. Also there are a couple of tools that works for apps from build to deploy so I want to discuss with dagger team about those, understand the key differentiators, that would be clearly help the community to understand what Dagger is and what it is not.

cloud canyon
autumn swallowBOT
#

Welcome @whole sierra!

autumn swallowBOT
#

Welcome @rugged inlet!

rugged inlet
#

Hi everyone!👋

winter linden
#

Thanks @vestal creek ! Sorry your deployment didn’t finish in time

vestal creek
#

I just checked ActivityMonitor

#

It's because Docker for Mac is using the new virtualisation framework

#

I need to disable that 😂

autumn swallowBOT
#

Welcome @lavish sinew!

autumn swallowBOT
#

Welcome @wary kraken!

autumn swallowBOT
#

Welcome @runic totem!

autumn swallowBOT
#

Welcome @spark shard!

autumn swallowBOT
#

Welcome @thick cedar!

autumn swallowBOT
#

Welcome @brazen cedar!

winter linden
#

Welcome everyone 🙂

winter linden
vestal creek
#

About 8 minutes after our stream it told me my netlify token was incorrect 😂

winter linden
#

ah damn. Usually it’s very fast I promise 😉

autumn swallowBOT
#

Welcome @swift barn!

autumn swallowBOT
#

Welcome @peak escarp!

autumn swallowBOT
#

Welcome @plain plinth!

autumn swallowBOT
#

Welcome @bronze storm!

bronze storm
#

Just came to appreciate how clean the docs & UI is

autumn swallowBOT
#

Welcome @foggy wharf!

autumn swallowBOT
#

Welcome @median mulch!

median mulch
#

Thanks for the invite, looks very interesting so far 🙂

winter linden
winter linden
autumn swallowBOT
#

Welcome @swift barn!

autumn swallowBOT
#

Welcome @ionic quartz!

winter linden
#

Summary: we used to implement dynamic environments on demand directly in the core Dagger tool. But we moved it out of the core, because there are lots of different ways to do it. Instead we exposed the primitives so you can implement it yourself in Cue 🙂

So you can implement ONE Dagger environment which dynamically deploys MULTIPLE instances of your app, one per git branch for example.

#

A common use case is to deploy a review environment on demand for each pull request

#

Dagger gives you all the building blocks to do this easily, but in a modular in a customizable way (instead of hardcoded in a monolithic tool)

swift barn
# winter linden Summary: we used to implement dynamic environments on demand directly in the cor...

Actually is what I was looking into... basically is the idea of implementing a simple ML (as in Machine Learning) pipeline that leverage some components to deploy the infrastructure and later deploy the pipeline itself. This micro-environment would take as input a git repo and would be re-triggered any time I change something (i.e. I commit a new model) I should be able to start a PoC on this next week. If anyone is interested I may open it as a issue/PR and upload my findings

winter linden
#

That would be great. Dagger is very well suited for this. You can create new issues, comment on #768, post here, whatever works. Happy to do a code review anytime 🙂

swift barn
#

Actually that was my first reason of spending time with Dagger after I saw your demo at Dockercon... components and DAG's are perfect for this. 🙂

autumn swallowBOT
#

Welcome @night bane!

autumn swallowBOT
#

Welcome @weary niche!

#

Welcome @random geyser!

night bane
#

Greetings 👋 Thank you for the invite! I am excited to start digging in. Right off the bat:

  • Cue seems like a great choice to me.
  • Very happy to see that the name dagger is a h/t to the almighty DAG
  • lots of potential for DevSecOps-centric integrations with tooling like OPA, in-toto, sigstore, and friends (301 to #🔭universe)
  • 👏 dagger doc
wraith niche
#

Does anyone have interest in easily deploying to AWS Lambda using a simple "app" abstraction package? I do for release tools but I am asking first to know if there are specific requirements for a new dagger package.

winter linden
turbid tulip
#

That was a great one!

autumn swallowBOT
#

Welcome @little lion!

autumn swallowBOT
#

Welcome @rustic brook!

autumn swallowBOT
#

Welcome @lofty basalt!

autumn swallowBOT
#

Welcome @zealous roost!

autumn swallowBOT
#

Welcome @upbeat marten!

autumn swallowBOT
#

Welcome @sly rover!

autumn swallowBOT
#

Welcome @robust hill!

#

Welcome @shrewd light!

#

Welcome @swift barn!

autumn swallowBOT
#

Welcome @surreal echo!

autumn swallowBOT
#

Welcome @analog pilot!

autumn swallowBOT
#

Welcome @gentle solar!

autumn swallowBOT
#

Welcome @swift barn!

silk apex
#

Hello French people

#

Don't forget we have a dagger event today starting in 10min

#
#

Join us!!!

autumn swallowBOT
#

Welcome @fast sinew!

silk apex
#

thanks a lot dagger team @winter linden @wraith niche @swift barn every attendees where mesmerized by dagger !

silk apex
#

oups 🙂 thanks @wraith niche

#

om my way to try something stupid 🙂

winter linden
winter linden
#

@cloud canyon @wraith niche still work in progress, but feedback welcome. One of those big items we’ve discussed a lot but didn’t have time to write down. I have to disconnect now but will finish writing it tomorrow. https://github.com/dagger/dagger/issues/793

winter linden
#

Added a whole section from my phone while in the car, but github ui lost it all because of bad reception 😩😭

sly palm
#

@winter linden 😳😭

autumn swallowBOT
#

Welcome @warm gull!

silk apex
winter linden
#

How do you all make those cool little gifs to illustrate a feature or problem in your github issues?

steel ether
#

Hi. Are invites still open? I would like to try dagger myself 🙂 . Here is my github account: https://github.com/axeII

cloud canyon
#

@steel ether Of course, can you DM me your email (so we can send the welcome email with the instructions)?

#

@steel ether you should have received the welcome email and have access to the repo, let me know if it works

swift barn
#

Seems my little Poc is going well Kubeflow pipelines installed and managed through dagger 🙂

winter linden
#

Wow! I hope you can show us a demo at the first virtual meetup 🙂

swift barn
#

Yep (wait when is the first virtual meetup?)..well now the real hard part... manage a more complex scenario with pipelines attached 🙂

winter linden
#

No date yet for the meetup… It’s on my todolist to organize it, but there’s so much to do!

swift barn
#

Ah ok ..I was thinking I missed some news 🙂 btw I can pick up some PR (like the easiest ones..I'm a Product Manager not a developer :D)

winter linden
#

Does anyone else have something they would like to show, or talk about, in a virtual meetup? (basically a few people on a discord live room)

winter linden
#

@everyone attention dear Dagger testers. If you have joined this discord before we had a registration form, please take a minute to register at https://dagger.io (click “request early access”).

Of course you already have access, but if you are not on the list, you will not receive updates from us: for example information about the first community meetup; new features; information about our roadmap; etc.

PLEASE REGISTER AT https://dagger.io if you haven’t done so!

Thanks!

#

(thank you to the many people who did this in under 3 minutes 🤗 )

cold river
#

You're welcome! 😄

lime sierra
winter linden
#

Thanks! Two-way compatibility between GHA and Dagger would be pretty amazing

  • Call Dagger in GHA ✅
  • Call GHA in Dagger 🤯😍
autumn swallowBOT
#

Welcome @drifting cypress!

#

Welcome @young bobcat!

cloud canyon
#

v0.1.0-alpha.18 is out 🚀

https://github.com/dagger/dagger/releases/tag/v0.1.0-alpha.18

New packages available: Google Cloud Run, Google Cloud Storage, Java/Maven, Docker Compose

Major UX changes:

  • The plan is not embedded in .dagger anymore (e.g. .dagger/env/XXX/plan). Instead, its location can be specified with dagger new myenv -p ./my/cue/package

  • A dagger workspace (e.g. the directory you dagger init-ed, where .dagger is located) is now a valid cue module. This means the cue CLI will work out of the box in any dagger workspace (e.g. you can cue eval the plan)

swift barn
#

So I did this super simple example of using dagger to run a Machine-Learning pipeline (after installing Kubeflow pipelines). If anyone want to give a try here it is the v1 (it misses a lot of optimization and other useful, practical stuff..): https://github.com/alefesta/dg-examples just copy the main.cue, dagger init, dagger new and you should be able to run dagger up (when the pipeline is printed check in the Kubeflow UI under runs your pipelines

GitHub

A simple set of examples. Contribute to alefesta/dg-examples development by creating an account on GitHub.

severe coral
#

Awesome @swift barn

swift barn
cloud canyon
#

🚀 v0.1.0-alpha.19 is out with a few minor changes (only been a couple of days since alpha.18)

  • Input validation (on dagger input * / dagger edit): Setting a wrong input (e.g. trying to squeeze a string into a secret, a number into a string, etc) will be rejected

  • Updated to buildkit v0.9.0-rc1

  • Moved from OpenTracing to OpenTelemetry (thanks @hoary spoke)

  • Performance improvement: we used to load/parse the CUE configuration 3 times during a dagger up, it's now only done once

  • Homebrew now downloads through a CDN, should speed things up a little bit (CloudFront Distribution)

winter linden
winter linden
silk apex
#

Anyone can suggest a good github client for Android? Fasthub is annoying with private repos

swift inlet
silk apex
#

😦

cloud canyon
swift barn
cloud canyon
#

Hopefully much sooner than that, otherwise it would mean that our documentation is really really bad 😛

swift barn
#

ahahah nah docs are great it's me .... 😄

shrewd jolt
#

is there a way to make cue not render the string "true" -> true the boolean

#

oh wait, i think that was just on an older version of cue

wraith niche
autumn swallowBOT
#

Welcome @swift barn!

#

Welcome @coral surge!

winter linden
autumn swallowBOT
#

Welcome @cinder field!

autumn swallowBOT
#

Welcome @oblique acorn!

#

Welcome @swift barn!

autumn swallowBOT
#

Welcome @swift barn!

#

Welcome @proud flicker!

autumn swallowBOT
#

Welcome @granite pewter!

autumn swallowBOT
#

Welcome @near matrix!

winter linden
#

Welcome everyone, have fun with Dagger. We’re happy to answer any questions.

autumn swallowBOT
#

Welcome @full ore!

autumn swallowBOT
#

Welcome @wispy goblet!

autumn swallowBOT
#

Welcome @quick lava!

autumn swallowBOT
#

Welcome @zinc coral!

autumn swallowBOT
#

Welcome @hasty umbra!

autumn swallowBOT
#

Welcome @woven jacinth!

autumn swallowBOT
#

Welcome @rotund acorn!

#

Welcome @stiff cloud!

autumn swallowBOT
#

Welcome @slender jay!

silk apex
#

@slender jay like Polini?

silk apex
#

Ah ah ah ah ah ah @winter linden !!!

slender jay
#

The one and only! Just like there's only one @silk apex

#

Hi! 👋

silk apex
#

Oh Holly Molly!!!, hey hey hey hey

#

So cool to see you around! @slender jay

#

Want to join the fun I guess? 😉

slender jay
#

Yea i've heard about this cool new thing called Dagger and had to check it out 😉

winter linden
#

You haven’t made it until Ashlynn joins your discord

silk apex
#

mmmmmeeeeeemmmmooooorrrrriiiieeeessssss

#

daggercon 2022?

#

Ashlynn as the MC? How about it @solomon? 🤣

autumn swallowBOT
#

Welcome @native lava!

winter linden
#

@silk apex we should probably start with a meetup before talking about a whole Con 😁

silk apex
#

@winter linden meetup done (OK in French)

#

Next step : workshop (in French)

#

And then daggercon (in France) 😜

autumn swallowBOT
#

Welcome @devout cradle!

#

Welcome @dim chasm!

autumn swallowBOT
#

Welcome @timber mountain!

autumn swallowBOT
#

Welcome @mystic mantle!

mystic mantle
#

Hi all

#

I have some projects (video game and app in Go) that I still haven't published/deployed. I guess it was good for me to wait for more than 3-4 years to take care of that :p
I'm gonna do it on dagger and see how fun it is 😄

#

(I know it is not in the install manual, but go installing the source don't work in module mode

go install -v github.com/dagger/dagger/cmd/dagger@latest
go: downloading github.com/dagger/dagger v0.1.0-alpha.20
go install github.com/dagger/dagger/cmd/dagger@latest: github.com/dagger/dagger@v0.1.0-alpha.20: verifying module: github.com/dagger/dagger@v0.1.0-alpha.20: reading https://sum.golang.org/lookup/github.com/dagger/dagger@v0.1.0-alpha.20: 410 Gone
    server response: not found: github.com/dagger/dagger@v0.1.0-alpha.20: invalid version: unknown revision v0.1.0-alpha.20
cloud canyon
#

Welcome @mystic mantle! Let us know if we can help somehow

cloud canyon
cloud canyon
cloud canyon
#

Go modules don’t like private repo a out of the box

mystic mantle
#

I'll check that, I used to use the trick in .gitconfig to transform any git clone in https://github.com to git@github.com: but I guess you're right, it shouldn't work for the modules

GitHub

GitHub is where over 65 million developers shape the future of software, together. Contribute to the open source community, manage your Git repositories, review code like a pro, track bugs and feat...

#

Getting

GOPRIVATE=github.com/dagger go install github.com/dagger/dagger/cmd/dagger@latest
go: downloading github.com/dagger/dagger v0.1.0-alpha.20
go install github.com/dagger/dagger/cmd/dagger@latest: github.com/dagger/dagger@v0.1.0-alpha.20
    The go.mod file for the module providing named packages contains one or
    more replace directives. It must not contain directives that would cause
    it to be interpreted differently than if it were the main module.
#

Anyway, git clone +go install ./cmd/dagger from the root directory worked flawlessly

dagger version
dagger devel () linux/amd64
cloud canyon
mystic mantle
#

Oh, I know about that, it was not ironic.
I wish go:embed could embed the revision directly in the binary (like from .git/refs/heads/main, that would avoid those extra steps

winter linden
winter linden
#

What’s your prefered terminology for “the people on the team who help developers ship their code”:

  • SRE
  • Devops engineer
  • Cloud engineer
  • Platform engineer
  • IT
  • Ops
  • other?
autumn swallowBOT
#

Welcome @stable forum!

native lava
winter linden
native lava
winter linden
#

Yeah I hear a lot from purists… Purists are always the loudest.

hoary spoke
native lava
autumn swallowBOT
#

Welcome @blissful bone!

blissful bone
#

Hi 👋

blissful bone
#

Everyday I build tools that help developpers (or devops teams) build, ship, control, secure and deploy their code to environments.
I think my title is "Tech Lead DevOps"
We are a team of 5/6 people in a "Devops Solutions" entity, that help many teams (maybe 300 people in ~20 entities)
Our job is to maintain CI/CD tools (scm, ci, release, quality, security, ...) and templates that people import to build/deploy apps on all our platforms
I'm interested on how dagger can help us in that, with a particular context of a big company (Insurance)

autumn swallowBOT
#

Welcome @slate heron!

autumn swallowBOT
#

Welcome @chilly parrot!

chilly parrot
autumn swallowBOT
#

Welcome @gray frigate!

winter linden
#

Welcome everyone! Thanks @chilly parrot for the links. Those look very interesting!

winter linden
autumn swallowBOT
#

Welcome @fading sparrow!

autumn swallowBOT
#

Welcome @alpine ether!

alpine ether
#

Excited to try out Dagger! Is it too early to think about contributing an integration?

#

Does anyone have some good canonical CUE example files to learn from?

alpine ether
swift inlet
swift inlet
autumn swallowBOT
#

Welcome @slim matrix!

full ore
#

Hi all, I'd like to learn more about usage patterns with dagger. The following cases are top of mind (Excuse the long-windedness, I have many questions):

  1. Deploying/Testing multiple microservices (and code repositories) as a single unit

As @winter linden mentions here, dagger can be used to orchestrate deploying multiple microservices that live in different repositories, on a test branch. (#dev message)

Is there an example somewhere demonstrating this pattern of deploying multiple microservices at once, using dagger?

  1. Multi-tenant application deployments

There are existing examples of using dagger to deploy different "environment" variations (i.e. dev, prod, etc.). A related problem when providing a multi-tenant service is deploying an app once-per-tenant. For example, I'd like to deploy a service (or set of services) for tenant/customer A, B, etc.

How might one achieve this multi-tenant deployment setup using dagger? I imagine the approach might be somewhat related to my first question above.


Related, some tools in the declarative infrastructure space advise keeping all of your declarative infrastructure manifests in a single repository, as opposed to keeping them "close to the app" (example: https://argoproj.github.io/argo-cd/user-guide/best_practices/#separating-config-vs-source-code-repositories).

Is it fair to say that dagger is pursuing the "infrastructure manifests live close to the app" pattern?

autumn swallowBOT
#

Welcome @fluid wave!

autumn swallowBOT
#

Welcome @blissful flower!

autumn swallowBOT
#

Welcome @hearty basalt!

autumn swallowBOT
#

Welcome @chrome dagger!

autumn swallowBOT
#

Welcome @pastel salmon!

autumn swallowBOT
#

Welcome @umbral glacier!

winter linden
umbral glacier
#

perhaps the comparison to other tools section of the docs could include terraform?

autumn swallowBOT
#

Welcome @warm schooner!

serene thistleBOT
#

(question originally posted on Discord by @jpugliesi)

Hi all, I'd like to learn more about usage patterns with dagger. The following cases are top of mind (Excuse the long-windedness, I have many questions):

  1. Deploying/Testing multiple microservices (and code repositories) as a single unit

As @shykes mentions here, dagger can be used to orchestrate deploying multiple microservices that live in different repositories, on a test branch. (https://discord.com/channels/70763653042405379...

umbral glacier
autumn swallowBOT
#

Welcome @ocean condor!

ocean condor
#

@umbral glacier thanks for posting on GitHub - looking forward to the discussion

winter linden
#

thank you both 🙂 I will prepare an answer!

autumn swallowBOT
#

Welcome @minor shell!

autumn swallowBOT
#

Welcome @rough zenith!

autumn swallowBOT
#

Welcome @edgy stream!

autumn swallowBOT
#

Welcome @swift barn!

autumn swallowBOT
#

Welcome @swift barn!

serene thistleBOT
#

There is much overlap between the roadmaps of Dagger and Cue. I thought it would be useful to have a catalog of those issues, and perhaps a centralized discussion thread would help us assemble that catalog together.

I’m not 100% sure whether this should be an issue or a discussion… But since it’s quite open ended, and it’s not obvious when this discussion should evet be “closed”… I am trying the discussion format.

Below is a list of tasks or workstreams which are needed by both Cue and ...

autumn swallowBOT
#

Welcome @swift barn!

umbral glacier
#

how does dagger compare to hashicorp waypoint? yet another episode in the series of "devops landscape is confusing"

autumn swallowBOT
#

Welcome @unreal elm!

wraith niche
serene thistleBOT
swift inlet
#

Hello everyone,
For the past 2 weeks, with @wispy tapir, we've been leveraging Dagger to create a new open-source application that will help you deploy lambdas / serverless apps on AWS easily 🥳

Think of this implementation as an open-source alternative to apex or serverless-stack.
Prior the aimed launch at the end of the week (🤞), we would love to have direct feedback from potential users (from the curious developer with no AWS knowledge to the Grand Master deploying 15+ per day). Either way, feel free to book a call anytime at https://calendly.com/guillaume-derouville

👌 if you're interested but don't have the time to setup a calendly
👎 if you think that it's not an interesting use case

unreal elm
#

@winter linden I Requested Early Access of dagger before, but now the invitation link has expired due to my mistake. How can I regain the invitation?

wraith niche
unreal elm
wraith niche
unreal elm
serene thistleBOT
#

Let's say that, using Dagger, someone develops an awesome package and wants to integrate it in his SAAS. What is the current way to do it ?

For example: a user clicks on a button (on a website) -> dagger runs with a specific package -> outputs are being sent back to the server, etc ...

Is it possible atm ? If yes, how do we integrate it ? If no, is it something that will be on our roadmap ?

wispy tapir
#

@wraith niche Maybe notification from Github discussion should be in a different channel ?

serene thistleBOT
stable forum
swift inlet
autumn swallowBOT
#

Welcome @cursive olive!

cursive olive
#

Hey everyone! Thank you for the invite.

cloud canyon
#

Welcome @cursive olive !

autumn swallowBOT
#

Welcome @junior spindle!

junior spindle
#

Hey there; fascinated to see more of Dagger. Been interested in the build space for a long time, and the last year has been about using CUE to manage my org's infra

cloud canyon
#

Welcome! Excited to have you onboard and curious about what you've been up to with CUE 🙂

junior spindle
#

I've been trying to find the Google Doc I read a year ago that served in part as the motivation.

#

Basically, trying to resolve the problem of using OTS and bespoke software in the same k8s cluster; I'd started with a Helm/Kustomize situation and it got quickly overwhelming with boilerplate.

#

At the time, the Kustomize docs mentioned CUE in passing, and while initially I'd resisted because it seemed overwhelming to add another tool, but once I started pulling CUE in things got easier... for a while.

#

Part of what I'm trying to work on now is a movement to abstracting Kustomize bases in CUE, so that they can be merged into a complete cluster variant.

#

But I'm stymied at the moment by CUE build times.

wraith niche
junior spindle
#

I'm pretty far down my path here; I have CUE generating Kustomize, a kustomize build (with a ChartInflator plugin), and then a kubectl apply in a little pipeline.

autumn swallowBOT
#

Welcome @swift barn!

swift barn
#

hello 👋 thanks for the invite 🙂

autumn swallowBOT
#

Welcome @mortal eagle!

mortal eagle
#

Hi dagger folks! My Github invite from @cloud canyon expired, is there any way to grab a new one? Maybe @wraith niche ? My Github username is rsynnest

wraith niche
mortal eagle
#

Thanks!

wraith niche
#

Is anyone, who did not get a chance to try out dagger yet, interested in being interviewed while going through the docs? We can take the advantage of that to talk about a specific project and help you build it.

autumn swallowBOT
#

Welcome @distant radish!

mystic mantle
wraith niche
autumn swallowBOT
#

Welcome @latent gust!

autumn swallowBOT
#

Welcome @tulip comet!

wraith niche
wispy tapir
#

👋 Hi everyone,

With @swift inlet , we want to share a solution to deploy serverless apps with dagger.
Under the hood, it's a superset of AWS SAM, helping you deploy applications on top of lambdas.
The package aims to be easy to use.

The project currently supports:

  • Easy lambda deployment (Zip / containers)
  • Inline lambda integration
  • API & SQS events
  • Layers
  • Automatic stack supply
  • API configuration
  • Secrets
  • Multiple lambdas

You can find more informations directly on our repository : https://github.com/grouville/dagger-serverless.
It contains READMEs, examples and tutorials to help you begin with the package.

Don't hesitate to test it and give us feedback on the github repo, here or live: https://calendly.com/guillaume-derouville 🚀

wraith niche
#

dagger v0.1.0-alpha.21 has just been released. Although it's a minor release that includes mostly bugfixes. The big highlight is the Azure support into the stdlib, thanks to @sly rover!

autumn swallowBOT
#

Welcome @void pumice!

wraith niche
#

dagger v0.1.0-alpha.22 is out - here are the highlights:

  • significant performance increase while listing inputs and overall dagger up
  • Azure Storage support (thanks @sly rover)
  • Inputs list is much easier to read (filters out optional values by default)
  • Other reliability fixes
turbid tulip
#

Thought people here might be interested in this: https://www.youtube.com/watch?v=0iN4dJB3OLk

In this episode, we take a look at the multi-platform super caching BuildKit and buildx

🍿 Rawkode Live

Hosted by David McKay / 🐦 https://twitter.com/rawkode
Website: https://rawkode.live
Discord Chat: https://rawkode.live/chat

#RawkodeLive

🕰 Timeline

00:00 - Holding screen

👥 About the Guests

Tõnis Tiigi

.

🐦 https://twitter.com/tonis...

▶ Play video
silk apex
#

congratz @sly rover 😄

fresh zephyr
#

Hey Dagger folk. I just noticed that the stdlib doesn't have any python modules, and I don't see any PR or issues for this. Is this something that should be added? I wouldn't mind writing up the cue for it.

wraith niche
fresh zephyr
wraith niche
fresh zephyr
#

It is indeed quite trivial, I've already done it (using os.#Container) to get myself introduced to dagger. I was just wondering if it would even be worth adding to the stdlib.

wraith niche
#

sorry I misunderstood. It's hard to give you a hint before looking at the code, but if it's not too much work to open a PR to stdlib, we can take a look. Other option is to wait for the next release, we'll have the support for external packages, so it'll be possible to publish a package (outside the stdlib).

winter linden
#

If you’re up for that contribution @fresh zephyr , adding a Python build component to the stdlib would be fantastic and greatly appreciated!

wraith niche
#

🚀 dagger v0.1.0-alpha.23 is out. Main highlight is the first version of the package manager. Dagger now has the ability to fetch remote packages and you can publish your own: https://docs.dagger.io/1011/package-manager/
Feedback is welcome as usual.

autumn swallowBOT
#

Welcome @quaint horizon!

winter linden
#

Hi there 🙂

autumn swallowBOT
#

Welcome @fathom cosmos!

fathom cosmos
#

Hi! I just got access so I'm going through the repo and docs.
@winter linden I saw your first steps with CUE on the CUE Lang Slack 2 years or so ago as I was dabbling with it myself to abstract away K8s config lol

#

I might schedule a chat with the team if that's okay to better grok the mental model and figure out how and what to play with.

winter linden
autumn swallowBOT
#

Welcome @late pivot!

late pivot
#

Hi all! Excited to try it out! Something like Dagger has long been needed

#

@winter linden you spoke at my YC batch like 6 years ago, was a great talk and I never forgot it, looking forward to seeing Dagger make as much of an impact as Docker 🙂

autumn swallowBOT
#

Welcome @mortal forum!

autumn swallowBOT
#

Welcome @naive kraken!

winter linden
winter linden
autumn swallowBOT
#

Welcome @native hinge!

autumn swallowBOT
#

Welcome @fathom atlas!

autumn swallowBOT
#

Welcome @mild laurel!

#

Welcome @stark hawk!

autumn swallowBOT
#

Welcome @digital pine!

autumn swallowBOT
#

Welcome @keen snow!

autumn swallowBOT
#

Welcome @swift barn!

wraith niche
#

Welcome everyone! If anyone needs help while going through the dagger docs (https://docs.dagger.io/), feel free to ask on #help-old-do-not-post - and if you want to chat live with someone from the team, there is a scheduling link in the topic channel. Always eager to hear feedback and provide some help.

autumn swallowBOT
#

Welcome @hushed bone!

autumn swallowBOT
#

Welcome @pliant crow!

wraith niche
#

🚀 dagger v0.1.0-alpha.24 is out. Mainly stability and security fixes:

  • stdlib/git supports commit/push (the stdlib will soon move out to separate repo and be managed as a external package)
  • packages are now able to output secrets to be re-used as inputs directly in the code (also added Secret support to DockerLogin)
  • stdlib/aws supports localstack - allows for local testing without relying on remote aws api (which increased the test coverage of the aws/* library)
  • various Docs improvements

As usual, if you want to bump de priority on some features, please share your feedback.

winter linden
severe coral
wraith niche
rocky flame
autumn swallowBOT
#

Welcome @silent agate!

autumn swallowBOT
#

Welcome @undone summit!

autumn swallowBOT
#

Welcome @grim flicker!

#

Welcome @thorn pulsar!

winter linden
#

You made it @thorn pulsar 🙂 Welcome

autumn swallowBOT
#

Welcome @charred bronze!

autumn swallowBOT
#

Welcome @terse cliff!

autumn swallowBOT
#

Welcome @floral fable!

autumn swallowBOT
#

Welcome @neat anchor!

neat anchor
#

ahoj

rocky flame
autumn swallowBOT
#

Welcome @neon umbra!

neon umbra
#

hey, hi all

#

thank you for the invitation

autumn swallowBOT
#

Welcome @slow sun!

#

Welcome @dire breach!

terse cliff
#

Hello Hello, happy to be here. Engineer from Mexico

winter linden
#

Welcome @terse cliff 🙂

terse cliff
#

Is this "Book a demo" free for anyone?

wraith niche
autumn swallowBOT
#

Welcome @swift barn!

autumn swallowBOT
#

Welcome @cunning hazel!

#

Welcome @uncut scroll!

autumn swallowBOT
#

Welcome @pine shadow!

autumn swallowBOT
#

Welcome @swift barn!

#

Welcome @blazing pagoda!

autumn swallowBOT
#

Welcome @swift barn!

swift barn
#

Hello folks 👋 Excited to be learning more about Dagger.

wraith niche
#

🚀 dagger dagger v0.1.0-alpha.25 is out.

Release highlights:

  • ArgoCD is now officially supported in the universe standard library (thanks @spark shard for contributing the code)
  • stdlib/gcp now supports secrets management (thanks @swift barn for the code contribution)
  • stdlib/kubernetes can now deploy kube config from a URL
  • Various docs & stability fixes
autumn swallowBOT
#

Welcome @west patrol!

silent agate
#

Who is using AWS? How are you deploying infrastructure? Cloudformation? CLI? For those not using Terraform can we talk?

autumn swallowBOT
#

Welcome @unkempt wigeon!

autumn swallowBOT
#

Welcome @orchid flax!

unkempt wigeon
#

Hi 👋
thanks for the invite. I'm excited to dive into Dagger and escpecially to see CUE in action with this project.

winter linden
#

Welcome @unkempt wigeon 🙂 If you have any questions or suggestions, don’t hesitate to send!

autumn swallowBOT
#

Welcome @errant harbor!

#

Welcome @noble viper!

winter linden
noble viper
#

my life for aiur 🤖 ty for having me ✌️

winter linden
#

I love the “continuous privacy compliance” use case @noble viper I think Dagger could be a natural enabler of that. CICD shouldn’t just be for pushing docker images and running kubectl

autumn swallowBOT
#

Welcome @sand patio!

autumn swallowBOT
#

Welcome @lilac burrow!

autumn swallowBOT
#

Welcome @normal vortex!

autumn swallowBOT
#

Welcome @wind crypt!

#

Welcome @swift barn!

#

Welcome @hexed grove!

#

Welcome @chilly raven!

autumn swallowBOT
#

Welcome @stable tartan!

autumn swallowBOT
#

Welcome @kindred flume!

autumn swallowBOT
#

Welcome @stiff whale!

unkempt wigeon
#

Hello @stiff whale ! \o/ good to see you here.

stiff whale
#

Hello my big friend @unkempt wigeon

autumn swallowBOT
#

Welcome @unique tapir!

unique tapir
#

Hello everyone from France 😉 Happy to join !

autumn swallowBOT
#

Welcome @swift barn!

autumn swallowBOT
#

Welcome @late heart!

autumn swallowBOT
#

Welcome @vast bone!

vast bone
#

👋 Hi everyone

wraith niche
#

Welcome everyone! Let us know if you need any help while going through the docs and code. Feel free to use the scheduling link in the channel's topic if you want to talk live.

autumn swallowBOT
#

Welcome @wraith sail!

winter linden
#

If anyone has feedback on the docs & tutorials, please send them to @silent agate who has volunteered to improve them, thanks Richard!

#

(discord or github issue are fine)

autumn swallowBOT
#

Welcome @heavy gazelle!

stable tartan
#

Just dagger up the todoapp, and looks like it's promising

silent agate
# stable tartan Just `dagger up` the todoapp, and looks like it's promising

good to hear! I'm curious did you find that example helpful to understand dagger? Was it effective for you to have an example ready to deploy out of the box? Just asking because we're considering starting with a "from scratch" demo where the docs walk you through the necessary steps to put the right code in the right place before running dagger up

winter linden
stable tartan
autumn swallowBOT
#

Welcome @nimble stone!

unkempt wigeon
silent agate
# stable tartan yes still I'm trying to understand `cue`.

working on some Cue documentation of our own. Here's the PR preview https://deploy-preview-985--devel-docs-dagger-io.netlify.app/1005/what-is-cue/

CUE is a powerful configuration language created by Marcel van Lohuizen who co-created the Borg Configuration Language (BCL)—the language used to deploy all applications at Google. It is a superset of JSON, with additional features to make declarative, data-driven programming as pleasant and productive as regular imperative programming.

autumn swallowBOT
#

Welcome @swift barn!

neat anchor
#

hey, this is a documentation page I would like to see:

How dagger works?
=================

1. Describe your deployment

* Create one or several cue files to describe your deployment
* With dagger, you describe how the infrastructure should be
* For example, one file describes the repository where is the code, one file containing netlify configuration, ...

2. Configure inputs and outputs

* dagger input list, dagger output list
* where data are saved?
* how does it work if you want to share these secrets among several developers?
* behind the scene, explain how @dagger(input) works

3. `dagger up`: the workflow engine

* Explain the algorithm of dagger to generate the DAG, how dagger decides which task is run first
* What is done with tasks "outside" the graph?
* Which tasks are run concurrently, which tasks are run sequentially?

what do you think?

#

Also, feature idea: dagger tree to display the DAG

autumn swallowBOT
#

Welcome @swift barn!

silent agate
neat anchor
#

super

autumn swallowBOT
#

Welcome @sharp apex!

autumn swallowBOT
#

Welcome @torpid tendon!

wraith niche
#

🚀 dagger dagger v0.1.0-alpha.26 is out.

Release highlights:

  • Support for a new input type dagger.#Stream - allows for deploying an app to a local docker daemon (a docs tutorial will follow soon, ping @silent agate if you have questions)
  • Terminology: dagger Workspace renamed to Project - the docs and the CLI reflect the changes
  • Added support for Azure Static Webapp in the Universe library (thanks to @sly rover)
  • Added support for dagger.#Secret in the docker build args (thanks to @spark shard)
  • Various bugfixes and security improvements - full release changelog: https://github.com/dagger/dagger/releases/tag/v0.1.0-alpha.26
winter linden
#

Native stream support is a big deal. In addition to injecting arbitrary artifacts and secrets into your pipelines, now you can inject arbitrary streams as well. For now it only supports unix sockets (for example your local docker socket) but in the future we will add other backends: tcp sockets (listen or connect), regular files, or output of executing a command.

#

Lots of fun use cases

autumn swallowBOT
#

Welcome @junior mantle!

autumn swallowBOT
#

Welcome @trail wyvern!

autumn swallowBOT
#

Welcome @swift barn!

autumn swallowBOT
#

Welcome @mint granite!

autumn swallowBOT
#

Welcome @wise saffron!

autumn swallowBOT
#

Welcome @worthy elbow!

#

Welcome @burnt depot!

autumn swallowBOT
#

Welcome @jaunty thorn!

jaunty thorn
#

Awesome to see y'all are on Discord too 😄

autumn swallowBOT
#

Welcome @smoky cove!

serene thistleBOT
#

Hi everyone 👋

A discussion about a use case with Nginx I thought about and the questions I have that are related to, I'm putting this in Q&A so that we could start looking at the prerequisites.

The context

So when I was working on a mission, we had several backend rest apis, protected by a gateway that requires the need of api keys to be passed by, a java gateway (serving as a layer of BFF with some security check with the JWT sent), an nginx reverse proxy (serving as another layer ...

autumn swallowBOT
#

Welcome @warm lion!

cloud canyon
#

Sneak preview of the new "live" console logger:

https://asciinema.org/a/t6ECOc14RGJTeb4oRki1k69Gv

It's much of an improvement over the current logger.

  • Rather than dumping a bunch of unrelated logs as they come, messages are grouped by CUE component and live updated in the terminal

  • Only the last few lines of each component are shown, so you can follow the progression of the entire config at once

  • Components that completed successfully are collapsed

  • In case of failure, all the logs are dumped

Recorded by aluzzardi

wraith niche
cloud canyon
#

So this is doing #2 and #3, still haven't addressed #1 but should be easy

mystic mantle
#

I was trying to add a shortcut to toggle my mute of mic and was looking for an unused key on my keyboard. I found one that Gnome called dagger AKA † .
I thought I would shared that in case you didn't know that utf-8 symbol.

#

Easy marketing with \u2020

#

Having used ⧓ for a while in all text input that accepted it, I can say it works. Also, because I wear bow ties. I guess wandering around conference grounds with a real dagger wouldn't have the same effect. 👮

patent stirrup
#

Does dagger have a logo yet and could I include it in a talk at kubecon? 🙂

winter linden
#

Ha ha of course

#

We finally have one

#

(credit to @mint axle for designing it)

patent stirrup
#

Nice!

#

@winter linden I’ve sent context in a pm

autumn swallowBOT
#

Welcome @swift barn!

winter linden
#

Hi all, one thing we noticed is that when you explain how you actually use Dagger, that explanation doesn’t match our own “official” explanation… So we’re adapting the official explanation to match your feedback 🙂

Here’s a first attempt, any feedback is welcome.

  • Does this explanation make sense to you?
  • Does it match your own use of Dagger?
  • If you understand Dagger today: would this explanation have helped you understand it better or quicker?
  • If you don’t think you understand Dagger: does this help?

https://github.com/dagger/dagger/pull/1030

swift barn
autumn swallowBOT
#

Welcome @umbral relic!

#

Welcome @grizzled geode!

autumn swallowBOT
#

Welcome @pastel patio!

#

Welcome @vocal lotus!

wraith niche
autumn swallowBOT
#

Welcome @ionic palm!

ionic palm
#

Hi everyone!

ionic palm
#

Can I please get invited again to dagger.io as my invite went to spam folder and got expired before I found it?

wraith niche
ionic palm
#

@wraith niche I've pm'ed you. Thanks

wraith niche
mystic mantle
#

being able to just create a few conf, initializing the vars and doing dagger up on different env is pretty rad.

#

So, my current need (not profesionnal) is to deploy a Go server on a dedicated server. It is available through ssh.
The order would be:

  • run the unit test/integration tests
  • create a docker image of this (with multi stage and distroless image)
  • push it to a private registry
  • on the server, pull the new image and docker-compose up
#

From what I read from the docker module, it already handles connecting to a remote docker via ssh. Am I right?

#

So it seems my use case is already available, it's just a matter of assembling the different config part?

winter linden
#

Yes I believe that’s correct.

#

Let us know if you run into any issues, or just need a sounding board 🙂

mystic mantle
wraith niche
wraith niche
silent agate
mystic mantle
winter linden
#

No you never want to create anything manually inside cue.mod. It’s entirely managed by Cue.

#

Similar to go.mod or go.sum

silent agate
autumn swallowBOT
#

Welcome @trim moss!

autumn swallowBOT
#

Welcome @quaint mica!

mystic mantle