Sent from phone, thus brief. Am 12.06.2015 16:11 schrieb "David Lang" <[email protected]>: > > On Fri, 12 Jun 2015, Rainer Gerhards wrote: > >> 2015-06-11 23:06 GMT+02:00 Brian Knox <[email protected]>: >>> >>> Florian - plan will probably depend on what we decide we're deploying. >>> Andre has set up an account already ( Rainer may have the details as well >>> ). We gave them access to the beta for the team account features - so it >>> should already be set up as a team account. We should make sure any >>> infrastructure we set up is provisioned from that account since we (DO) >>> have applied quite a bit of credit to it. >>> >>> If we're just working together on how we'd like to automate package >>> building I'd suggest a small server to start with and if we grow out of it >>> we can bump it up.. maybe the 2GB ram / 2 core / 40GB ssd option to >>> prototype on? Hard to know until we nail down exactly what we're trying to >>> stand up. >> >> >> OK, I think I'll simply provision such a machine (so I finally get my >> hands on your interface as well ;)). Does the NYC datacenter sound >> good given our collaborator base? > > > I don't think the collaborator base needs to drive the datacenter, we'll be working via git/ssh/etc anyway.
Lol, you know I am an old fashioned guy ;) but I was more thinking on internet closeness ... But agreed that's also yesteryears ;) Rainer > > David Lang > >> What do you think makes most sense from a file system structure point >> of view? I have something along this on my mind: >> >> /home/... >> pkgproject - packaging project user (also for cron jobs) >> rainer >> brian >> andre >> florian >> .... >> >> under pkgproject, I'd create subdirs for each git repository. >> >> Once done, I'd see that I can migrate my current daily build >> environment to that machine. That will probably raise questions, it's >> currently tied to the result of testbench runs. Maybe issues to >> discuss... Let's assume this works then we can begin to modify it in a >> way that suits us better. >> >> It would probably good to describe the environment I use. I could do a >> Hangout on that, but I am not sure if I have sufficient time the next >> days and enough advance notice timeframe to make it fully interactive. >> >> Comments? >> >> Rainer >> _______________________________________________ >> rsyslog mailing list >> http://lists.adiscon.net/mailman/listinfo/rsyslog >> http://www.rsyslog.com/professional-services/ >> What's up with rsyslog? Follow https://twitter.com/rgerhards >> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT. >> > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
