SoylentNews is people
SoylentNews
from the good-business-or-something-else dept.
https://www.cnbc.com/amp/2018/06/01/microsoft--github-acquisition-talks-resume.html
Microsoft held talks in the past few weeks to acquire software developer platform GitHub, Business Insider reports.
One person familiar with the discussions between the companies told CNBC that they had been considering a joint marketing partnership valued around $35 million, and that those discussions had progressed to a possible investment or outright acquisition. It is unclear whether talks are still ongoing, but this person said that GitHub's price for a full acquisition was more than Microsoft currently wanted to pay.
GitHub was last valued at $2 billion in its last funding round 2015, but the price tag for an acquisition could be $5 billion or more, based on a price that was floated last year.
(Score: 3, Funny) by MichaelDavidCrawford on Saturday June 02 2018, @05:48PM (5 children)
How hard is it for me to set up my own Git server? I can't be bothered to google a tutorial.
Yes I Have No Bananas. [gofundme.com]
(Score: 4, Touché) by tomp on Saturday June 02 2018, @06:02PM (2 children)
It's way harder than googling a tutorial. Safe to assume you can't be bothered to set up your own Git server either.
(Score: 3, Disagree) by JoeMerchant on Saturday June 02 2018, @07:05PM (1 child)
Tutorial for Ubuntu:
sudo apt-get install git
mkdir repo.git
cd repo.git
git init --bare
and, if you haven't disabled the default ssh server, your repo is live and ready to use. There are, of course, several hundred nuanced security considerations - all left as an exercise for the reader. Basically: if you're going to start giving people access to your machine via the ssh server - handle your ssh server with all due care. Personally, I like creating a git user with the git (no command line access) shell and only exposing ssh access to that, and requiring my outside users to give me their public ssh key so I can add them to the /home/git/.ssh/authorized_keys file - hopefully the git user's shell access is limited enough that my repo users can't monkey with the authorized_keys file, hmmm.....
🌻🌻 [google.com]
(Score: 2) by MichaelDavidCrawford on Sunday June 03 2018, @12:38AM
I have a useful command line tool that I've decided to release as Free Softwary
Yes I Have No Bananas. [gofundme.com]
(Score: 3, Informative) by requerdanos on Saturday June 02 2018, @06:16PM
I am pretty sure, don't use me as a tutorial or anything, that a "git server" is a computer that you have ssh access to, with one or more local git repositories on it that you have permission to access.
(Score: 4, Informative) by JoeMerchant on Saturday June 02 2018, @06:57PM
If you've got a box that's running any flavor of Linux, it's about 2 minutes to get a git server working, and maybe 30 to think through a few security issues you'd want to nail down before opening a hole in your firewall to let the internet in to get at it.
All in all, I'd recommend a minimum of 2 hours dedicated research time on Google to get to know about the issues before setting up your own - I've set up an exposed git repo to work with some consultants overseas, neither of our corporate IT departments could manage to navigate their bureaucracy in any kind of timely fashion to expose a port to a company server so we could collaborate that way, so I punched a hole in the home firewall and exposed my laptop - we still mirror to the company repositories, but when we want to sync with each other we go through my laptop.
🌻🌻 [google.com]