path: root/doc/forum/build_propellor_binary.mdwn
diff options
authordesired.mta@88576fa3c90538abed47d3f0aa48d00bcc903b232019-04-11 15:40:17 +0000
committeradmin2019-04-11 15:40:17 +0000
commit57e6d49b9a26264e672f34d5f5c0747d0ea9cc4a (patch)
tree538ec3ec5840456849feb9c68a97d88d20ad0721 /doc/forum/build_propellor_binary.mdwn
parent37cc25e203f5732f99beaf8b3d82ec2855e017dc (diff)
Diffstat (limited to 'doc/forum/build_propellor_binary.mdwn')
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/forum/build_propellor_binary.mdwn b/doc/forum/build_propellor_binary.mdwn
new file mode 100644
index 00000000..e8f6e771
--- /dev/null
+++ b/doc/forum/build_propellor_binary.mdwn
@@ -0,0 +1,13 @@
+I'd like to run propellor differently:
+- create a static binary from `config.hs`.
+- upload it to the target machine (which can be ARM, do not have GHC, et al).
+- run it.
+Propellor would build the binary if I ask it to with `propellor --build`; not static yet, but I think I can figure it out.
+How would I run a propellor binary on the local host, without trying to connect anywhere? I would be grateful if you could suggest an approach.
+Thank you!