1 |
> What ive done on one of my servers is created a git user account that |
2 |
> cant login interactively, or with a password. (nologin), whoever needs |
3 |
> access gives me their private key and i add it to the authorized_keys |
4 |
> for the git account. |
5 |
> |
6 |
> This is obvoiusly very basic and you could create users for each |
7 |
> project etc, or use one of the many git server programs that will |
8 |
> allow to have more fine grained access control, Just depends on your |
9 |
> needs. |
10 |
> |
11 |
> For chat, ive used campfire for the chicago marathon, its not much |
12 |
> more than a glorified irc system. IRC is perfectly fine if your on a |
13 |
> closed network. but i would keep it off the general internet. |
14 |
|
15 |
An IRC server shouldn't listen on an internet-facing port? Are there |
16 |
security issues? |
17 |
|
18 |
- Grant |
19 |
|
20 |
|
21 |
> resource and task management, i think eclipse and some ides have |
22 |
> integrated solutions, outside of that not really sure |
23 |
> |
24 |
> - -Kevin |