Gitlab is moving from Microsoft Azure to Google Cloud Platform mainly due to its integration with Google Kubernetes Engine. Gitlab believes Kubernetes is the future and makes their platform to massively scale as it grows. The move is scheduled on July 28. Gitlab plans to use their Geo product for the migration of Gitlab.com. For more, read the article.
Microsoft acquired Github today for $7.5 billion. Github was founded in 2008. It stores and manages code in repositories using Git, a distributed version control software developed by Linus Torvalds. It has 28 million users and 85 million projects. Github public repositories are free. Private repositories start at $7 per month for developers. For teams, it starts at $9 per user/month and up to $21 per user/month. If you like to run your own Git repository, check out GitLab. Just install it on a Linux server.
Git is the most popular version control software for managing your code. If you’re looking for the best version control system out there, Git is the pretty much the de-facto standard of version control. Although you can run Git locally without a server, you’ll need some kind of repository to share your code with others.
Enter Github. Github provide free and paid Git repositories. Github public repositories are free, while private ones require subscription. For $7 dollars a month, you can have up to 5 private repositories. For $50 per month, you can use up to 50 repositories.
If you want to run your own Git repository either on the cloud or on your own private network (it’s more secure this way), then you’ll need to look at Gitlab’s Community Edition (Github.com is proprietary). Gitlab requires that you install their software on a Linux server (I’m using Ubuntu Server).
I tried running Gitlab CE on the cheapest server ($5 per month) I can find at Digital Ocean. It works but, it’s painfully slow. I don’t recommend it. The $5 per month server only has 1 CPU core and 512 MB of RAM. I recommend that you go for a system that has 2 CPU cores and 2GB of RAM. This system will cost $20 per month.
By the way, if you don’t want managing your own server, you can simply sign up with Gitlab.com. It’s free! They offer unlimited private and public repositories up to 10GB of disk space per project. Of course, Gitlab has other products. For a paid subscription you can get enterprise support and more advanced features.
Visit Gitlab for more details.
I made a mistake by publishing my database password to an environment file that’s visible. Rookie mistake. Replacing the database password entry with something else and submitting kinda takes care of the problem, but anyone can still view the history of the file and see your password. One way of getting rid of this, if you don’t really care about the history of your submits, is to reinitialize the project back to the initial commit. Here’s how.
// Clone the project to your local computer $ git clone https://github.com/name/myproject.git // go to your project directory $ cd myproject // delete the .git folder where all the history is kept $ rm -rf .git // reinitialize your repository $ git init // add Github url $ git remote add origin https://github.com/name/myproject.git // verify remote $ git remote -v // Add all files and commit the changes $ git add --all $ git commit -am 'initial commit' // Finally, push to the origin server which is Github $ git push -f origin master
Your sensitive data is now gone from history. Just be careful next time.
You can ignore specific files in Git by placing a .gitignore file at the root of your local repository. The files listed in .gitignore will not be tracked by Git. Why would you do this? Well, there are certain OS generated files placed in system folders such as .DS_Store or Thumbs.db that are not really part of your code.
Create a .gitignore file
Edit the .gitignore file
sudo nano .gitignore
Add the files you want excluded. You can use wildcards.
.DS_Store Thumbs.db *.log
Commit and Push
git commit -m "adding .gitignore file" -a git push
That should do it!
I’ve been using Mac OS 10.9 Mavericks for a couple of weeks now. So far, so good. No issues whatsoever. There were several updates that followed the OS upgrade. Updates to iTunes, iMovie, iPhoto were the obvious ones, plus a couple of other small applications that were also updated as a result of the OS upgrade.
I happen to use Git for version control for my software projects. One thing I noticed after upgrading to Mavericks, Git stopped working completely. I tried to do a git pull, and I was met with this error, “xcode-select: note: no developer tools were found at ‘/Applications/Xcode.app’, requesting install. Choose an option in the dialog to download the command line developer tools.”
The cool part about all this is, Mavericks immediately recognized the problem and offered to correct it by asking the user to proceed with Xcode installation. I gladly clicked Update/Install. The update took less than 5 minutes to complete. After the install, I issued git pull command again, and sure enough the my git repository updated nicely.
I’m glad to report that after two weeks running on Mac OS Mavericks, I haven’t had any major problems, except for this relatively minor inconvenience of reinstalling Xcode.