Login

Recent searches

No recent searches

Search options

Only available when logged in.
fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

fosstodon.org: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

#flake

1 post1 participant0 posts today
Public
shur3d

Being soaked into the vortex, running it on my , entertainment-pc in the shed and now even on my ancient sony vaio tablet, mounted to my rowing machine

Touch Screen and bluetooth Earbuds in perfectly working and with youtube playlists running smooth

It just runs efficiently, perfectly declarative to only run stuff needed, all organzied via local instance using "one to rule them all"

Cant wait for the next rowing session powered by 🚣 ❄️

Public *
Atemu

If you're a nerd like me and have just bought a #kobo #elipsa #ereader and want to set it up offline, there's an amazing repo by Michal Ulianko which automatically sets up sideload mode, firmware updates and handwriting recognition for you.

You need to supply it with firmware, iink and fonts files, modify the script a little to install to the correct path and only install the things you actually want but then it just works.

All wrapped with a handy little #nix #flake.

codeberg.org/Uli/kobo-elipsa-2

Codeberg.orgkobo-elipsa-2e-setupkobo-elipsa-2e-setup
Public
Orkulus

Just spent the evening setting up a multi host on my new .

I was able to replicate my desktop config pretty easily. I’ve been trying NixOS on my desktop for a few months and I haven’t had any major issues.

IMO the language can be quite opaque at times and has a pretty steep learning curve. I feel like I’m doing a lot more forum diving than on other distros.

Public
Jons Mostovojs

I spent four days learning #rust-adjacent toolchains (of which there are four, which are doing some things that are the same and some things that are different: #naersk, #fenix, #rustPlatform, #nixpkgs.#rust).

Throughout these four days I have seen at least a dozen of different error messages. Not a single error message had **anything whatsoever** to do with the error site. Reading traces helped, sometimes, but not always.

If you are a company who has excess money and you want to make the world a better place, please have your R&D department pick up #purenix, I urge you.

I ended up downgrading my whole *large* codebase to #rustStable and simplifying my #flake to:

```nix
{
description = "Flake for building rootrunner with standard nixpkgs Rust and OpenSSL support";

inputs = {
nixpkgs.url = "github:NixOS/nixpkgs";
flake-utils = {
url = "github:numtide/flake-utils";
inputs.nixpkgs.follows = "nixpkgs";
};
};

outputs = { self, nixpkgs, flake-utils, ... }:
flake-utils.lib.eachSystem [ "x86_64-linux" ] (system:
let
pkgs = import nixpkgs { inherit system; };
in
{
devShells.default = pkgs.mkShell {
buildInputs = with pkgs; [
rustc
cargo
rustfmt
clippy
rust-analyzer
pkg-config
sqlx-cli
postgresql
sqlite
nodejs
pnpm
zip
unzip
rsync
openssl.dev
openssl
];
};

devShell = self.devShells.${system}.default;
}
);
}
```

ExploreLive feeds
About