summaryrefslogtreecommitdiff
path: root/doc/forum/chown:_invalid_group:___8216__com-sixs:com-sixs__8217__/comment_2_c4453a2fe31d52ce0c5e6e615f1b18b2._comment
blob: 1442b72aa1c64fce6f82a5cc9571d88ed47b673b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
[[!comment format=mdwn
 username="joey"
 subject="""comment 2"""
 date="2019-02-13T21:48:30Z"
 content="""
Make that into a git patch and I will merge it.

However.. If you `git grep userGroup` you will find all the other places
that propellor assumes a user-group system. Seems it would be worth fixing
those too, especially the other ones in Ssh.

Seems like another approach to it could be to make
`userGroup`'s behavior configurable based on another Property
of the Host that sets Info containing say, a function from `User -> Group`.
Looks to me that would be doable, if a little bit annoying since userGroup
would need to change from a pure function to a Propellor action in order to
use `askInfo`.
"""]]