Fully decoupled. I have a close eye on Rust web frameworks but so far they seems not as production ready as good old TypeScript. Leptos is the one I would like to use if it become more mature in the future.
It sounds like you don’t want a dev container but a dev shell. Have a look at Nix flakes. This allows you to ship your dev environment as code but without the hassle of running inside a container. All your local tools will work and pickup whatever you configured in the flake.
Many small companies use it for their internal crates, as kellnr builds and host the corresponding rustdocs, too. Another prevalent use-case is as a crates.io cache to speed a build times or lower the network traffic.
I've the same feeling about sub-issues. I don't want the corporate pain of Jira to be replicated in Github. If you can't structure one issue to be comprehensive, multiple sub-issues won't help you either.
Just released Kellnr (https://kellnr.io) 5.2.6 with some bug fixes. I really wish I had more time for new features but at the moment my spare time is rare. If you want to host your own crates on your own infrastructure, check it out.
So it seems to me that the development shell does not pick up the certificates installed on the system. I can work around that by using an impure shell, but I think that this is not how nix should be used.
I use that too. Unfortunately it does only work with Docker and on some machines I've only containerd+nerdctl available. Would be cool if test containers supports more than Docker as a runtime.
We used labels to tag the workers with "arm" and "x86". We than used policies to allow applications to run only one or the other or both.
Hi! Sorry that happened. Feel free to ping an issue that was closed silenty but should not have been. I'll have a look.
Fully decoupled. I have a close eye on Rust web frameworks but so far they seems not as production ready as good old TypeScript. Leptos is the one I would like to use if it become more mature in the future.
Great video. Short and descriptive.
23 Millionen Euro ist auch eine Ansage. Ob das Geld nicht wonaders in Bochum besser aufgehoben wäre?
Haha, yeah you are right. I thought I added one. Here is the link: https://codeberg.org/secana/ForgejoKit
Cool little trick!
It sounds like you don’t want a dev container but a dev shell. Have a look at Nix flakes. This allows you to ship your dev environment as code but without the hassle of running inside a container. All your local tools will work and pickup whatever you configured in the flake.
Great, will upgrade right away. Thanks for sharing!
Thanks! Happy to hear that!
From everything I’ve tried so far, Claude is by far the best coding AI. Seems like others have the same impression.
Many small companies use it for their internal crates, as kellnr builds and host the corresponding rustdocs, too. Another prevalent use-case is as a crates.io cache to speed a build times or lower the network traffic.
I've the same feeling about sub-issues. I don't want the corporate pain of Jira to be replicated in Github. If you can't structure one issue to be comprehensive, multiple sub-issues won't help you either.
I see. Thanks for the answers. Guess it’s time to spend some money 😔
As mentioned on Mastodon (https://mastodon.social/@dpom@fosstodon.org/113460954769241417) there seems to be no way to do it at the moment :(
An honorable goal 😀
Just released Kellnr (https://kellnr.io) 5.2.6 with some bug fixes. I really wish I had more time for new features but at the moment my spare time is rare. If you want to host your own crates on your own infrastructure, check it out.
Thanks, I'll try that!
Sure. I import the certificates like this:
where
home.pemis a default PEM formatted certificate. It works fine to import the cert system wide this way.If I enter the flake.nix and run a simple
curlagainst the remote server I get the following, which is typical for a TLS certificate error.So it seems to me that the development shell does not pick up the certificates installed on the system. I can work around that by using an impure shell, but I think that this is not how nix should be used.
I use that too. Unfortunately it does only work with Docker and on some machines I've only containerd+nerdctl available. Would be cool if test containers supports more than Docker as a runtime.