diff options
| -rw-r--r-- | README.md | 22 | ||||
| -rwxr-xr-x | rise | 4 | ||||
| -rwxr-xr-x | serval | 5 | ||||
| -rwxr-xr-x | tidy | 2 |
4 files changed, 4 insertions, 29 deletions
@@ -61,31 +61,17 @@ handle the file. So for example: ## Development -A user can push code to any branch prefixed by `user/$USER/`. This is -set in the `gitolite-admin` repo which everyone with an account should -have read access to. This is also where your git ssh key is set. - To build code, do: - nix build -f default.nix <thing> + bild <ns> -To get in the environment for a thing, use `nix run`. For example, if -you want `ghci` with packages for `ibb`, do this: +To get in the environment for a thing, `repl`: - nix run -f default.nix Com.InfluencedByBooks.Server.env && ghci + repl <ns> And to deploy: - nix copy --to ssh://root@simatime.com ./result - ssh root@simatime.com $(realpath ./result)/bin/switch-to-configuration switch - -These three common tasks are captured in the `./bild`, `./ghci`, and -`./push` scripts. - -There's also a prototype `./rise` script which builds and runs an app. I -use it like: - - ag -l | entr -r ./rise Com.InfluencedByBooks + push <ns> <url> TODO: document how we use the following: @@ -1,4 +0,0 @@ -#!/usr/bin/env bash -nix build -f default.nix "$@".app -STATIC_DIR=$(realpath ./result/static) -./result/bin/ibb @@ -1,5 +0,0 @@ -#!/usr/bin/env bash -# -# deploy serval instance -# -./bild Com.Simatime.Serval && ./push Com.Simatime.Serval serval.simatime.com @@ -1,2 +0,0 @@ -#!/usr/bin/env bash -rm -f ./result* |