summaryrefslogtreecommitdiff
path: root/doc/forum/Propellor_without_superuser_privileges.mdwn
diff options
context:
space:
mode:
authorspwhitton2014-12-26 12:24:16 +0000
committeradmin2014-12-26 12:24:16 +0000
commit493d61d2289538069e8a5739195d01b04b3251ed (patch)
treeca27d4031f6d3ac14b4365d197be8c6559741748 /doc/forum/Propellor_without_superuser_privileges.mdwn
parent165980fdd3c994bbe207f20987cf437d67750bd4 (diff)
create forum post
Diffstat (limited to 'doc/forum/Propellor_without_superuser_privileges.mdwn')
-rw-r--r--doc/forum/Propellor_without_superuser_privileges.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/Propellor_without_superuser_privileges.mdwn b/doc/forum/Propellor_without_superuser_privileges.mdwn
new file mode 100644
index 00000000..d7288a72
--- /dev/null
+++ b/doc/forum/Propellor_without_superuser_privileges.mdwn
@@ -0,0 +1,3 @@
+Joey uses propellor to popular his /home/joey on hosts he controls. I'd like to use it to populate my home directory on hosts where I don't have root. If someone gives me a shell account on a Debian box, it would be great to just run `propellor --spin` to have apply properties such as having certain stuff downloaded and compiled in `~/local/bin`, putting cronjobs in place, and checking stuff out with `myrepos`.
+
+Does propellor assume root access at a deep enough level that writing properties to do this stuff would be impractical?