diff options
| author | Ben Sima <ben@bsima.me> | 2019-11-01 21:35:00 -0700 |
|---|---|---|
| committer | Ben Sima <ben@bsima.me> | 2019-11-01 21:35:00 -0700 |
| commit | d99f757fa37080eabc7c5cd258251c1bc12165cb (patch) | |
| tree | 7f0a2355ab26c276c13bdafac81b6b2c60bc3845 | |
| parent | cd84f6d36ff403d64860e524504a4f05a4e81adf (diff) | |
add build and deploy instructions
| -rw-r--r-- | README.md | 13 |
1 files changed, 8 insertions, 5 deletions
@@ -15,11 +15,14 @@ well-defined. Likewise, the functionality and purpose of a particular namespace should be small and well-defined. Following the unix principle of "do one thing and do it well" is advised. -Namespaces refer to conceptual boundaries. Implementations can be in any number -of languages, indicated by the file extension. For example, we can have -`com.example.api.hs` and `com.example.api.scm` in order to have an API client in -both Haskell and Scheme. Building `com.example.api` should compile both pieces -of code. +To build code, do: + + nix build -f default.nix <thing> + +Deploy: + + nix copy --to ssh://root@simatime.com ./result + ssh root@simatime.com $(realpath ./result)/bin/switch-to-configuration switch # Goals of the developer workflow: |