Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: NixOS/nixops
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: ba0c3f6c257a
Choose a base ref
...
head repository: NixOS/nixops
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 6f4f4da9537e
Choose a head ref
  • 2 commits
  • 4 files changed
  • 2 contributors

Commits on Apr 16, 2020

  1. Copy the full SHA
    6e2e287 View commit details
  2. Merge pull request #1284 from adisbladis/plugin-cleanup

    Remove remnants of pre-poetry2nix plugins
    grahamc authored Apr 16, 2020
    Copy the full SHA
    6f4f4da View commit details
Showing with 6 additions and 327 deletions.
  1. +6 −27 README.md
  2. +0 −86 all-plugins.txt
  3. +0 −17 data.nix
  4. +0 −197 update-all
33 changes: 6 additions & 27 deletions README.md
Original file line number Diff line number Diff line change
@@ -15,45 +15,24 @@ machines in a network or cloud.
To start developing on nixops, you can run:

```bash
$ ./dev-shell --arg p "(p: [ p.plugin1 ])"
$ ./dev-shell
```

Where plugin1 can be any available nixops plugin, and where
none or more than one can be specified, including local plugins.
An example is:


```bash
$ ./dev-shell --arg p "(p: [ p.aws p.hetzner (p.callPackage ../myplugin/release.nix {})])"
```

Available plugins, such as "aws" and "hetzner" in the example
above, are the plugin attribute names found in the data.nix file.

To update the available nixops plugins found in github repositories,
edit the all-plugins.txt file with any new github plugin repositories
that are available and then execute the update-all script. This will
refresh the data.nix file, providing new plugin attributes to use.

Local nixops plugins, such as the `callPackage ../myplugin/release.nix {}`
example seen above, have no need to be in the all-plugins.txt
or data.nix file.

## Building from source

The command to build NixOps depends on your platform and which plugins you choose:
The command to build NixOps depends on your platform you choose:

- `nix-build release.nix -A build.x86_64-linux --arg p "(p: [ p.plugin1 ])"` on 64 bit linux.
- `nix-build release.nix -A build.i686-linux --arg p "(p: [ p.plugin1 ])"` on 32 bit linux.
- `nix-build release.nix -A build.x86_64-darwin --arg p "(p: [ p.plugin1 ])"` on OSX.
- `nix-build release.nix -A build.x86_64-linux on 64 bit linux.
- `nix-build release.nix -A build.i686-linux on 32 bit linux.
- `nix-build release.nix -A build.x86_64-darwin on OSX.

Similarly, using NixOps from another project (for instance a nix-shell) can be done using:

```nix
stdenv.mkDerivation {
name = "my-nixops-env";
buildInputs = [
(import /path/to/nixops/release.nix { p = (p: [ p.plugin1 ]); }).build.x86_64-linux
(import /path/to/nixops/release.nix { }).nixops.x86_64-linux
];
}
```
86 changes: 0 additions & 86 deletions all-plugins.txt

This file was deleted.

17 changes: 0 additions & 17 deletions data.nix

This file was deleted.

197 changes: 0 additions & 197 deletions update-all

This file was deleted.