Add Nix flakes support through direnv

[superherointj]

Add Nix flakes support through direnv

Background

• Nix (https://nixos.org) is a reproducible build system. Having Nix support enables Nix users to develop and use Auto-GPT without having to deal with inner dependencies (such as PIP or any other future Auto-GPT dependency).

• To avoid Nix pollution to Auto-GPT repository, I have made Nix files a discrete repository:

  • github.com/superherointj/nix-auto-gpt

• Note: This only affects nix / direnv users and direnv explicitly requests permission from user to enable this.

.envrc file is used by direnv (https://github.com/nix-community/nix-direnv)
When direnv is installed and configured, this script runs when openning directory.
It first checks for nix shell, then direnv explicitly request user permission once to load dependencies.
Onwards direnv will automatically load dependencies on entering directory.
Eliminating the need of "nix develop github:superherointj/nix-auto-gpt" for Nix users.

Changes

Documentation

Test Plan

To test:

• Have Nix (with Flakes) and direnv installed.
• Open Auto-GPT repo directory.
• direnv will request permission.
• Then, all project dependencies are loaded automatically.

PR Quality Checklist

• My pull request is atomic and focuses on a single change.
• I have thoroughly tested my changes with multiple different prompts.
• I have considered potential risks and mitigations for my changes.
• I have documented my changes clearly and comprehensively.
• I have not snuck in any "extra" small tweaks changes

[dhensen]

I missed this PR, so I'm late to the party, but I feel like merging this feels a little pre-mature. Let me explain why.

First, I don't want to attribute bad motive to @superherointj, the discrete repository looks good quality and as a user you look trustworthy.

But what happens when this repository suddenly contains malicious code/script? Maybe at least pin the commit that is being used, so that you can consciously screen the versioned code first before upgrading to latest.

What do you think @p-i- @richbeales @nponeccop ?

[superherointj]

But what happens when this repository suddenly contains malicious code/script?

If repo had malicious code it wouldn't be executed by default. Unless user granted permission through direnv.
This would only affect the subgroup of Nix users that have enabled direnv and explicitly allowed to fetch dependencies.

Maybe at least pin the commit that is being used, so that you can consciously screen the versioned code first before upgrading to latest.

Then, for every change of package (and there may be many as things are going), it would also mean making a PR to Auto-GPT to bump hashes. I don't know if that is a good flow. Specially at current rate things are changing.

I wouldn't mind if the repository was under Auto-GPT ownership and some review process would take place. But then,
if reviews are mandatory it would require having several Nix maintainers to approve each other PRs. I think it's a bit early to change this. But once there is a thriving community around the repo, it makes sense.

[superherointj]

Let me know if you want repository ownership to be transferred to Significant-Gravitas.
I'd prefer to keep commit rights until there are enough Nix maintainers to review each other PRs.