I missed a few things I wanted to go over with GitLab, and I have an update on trying out CACerts.
I didn't really go over GitLab or git itself and why it's important.
To understand GitLab, first you have to understand git. Git is a revision control software for plain text files. What this means is, you edit the code, commit your changes, and edit it again, and your code changes are tracked. Linus Torvalds, the creator of the Linux kernel created it when he wasn't happy with the other software that was available. Git is one of my personal favourite tools to use, and has helped me with development a ton. I've definitely made poor choices in improving code or deleting code I didn't like and want to undo that- with proper use of git this is trivial. One really advantageous feature of git is that it's decentralized- when you clone a project with git, all its contents are self contained on your computer and if you want to update with a remote server you can pull the changes from the server or push your changes to the server. You can even have multiple remote repositories to push and pull from, though in practice you won't use that feature too much. Another useful feature is you can set the remote repository to be another location on your local machine- this can be useful if you're away from the internet and worried about accidentally ruining your working directory.
GitLab is probably the best free software alternative to Github. Github is a web front-end for remote git repositories, bring a lot of additional features to git such as editing your code from the web, forking other projects and pushing changes back to main projects (useful for feature development), easy account and group management, and of course the advantage of keeping your code stored on a remote server in case of issues with your local machine. For an example of a Github project, you can check out the CS-401 project from Spring 2013 that I was a member of. GitLab offers pretty much all of Github's main features and a familiar interface. The big advantage of GitLab over Github is that we can store the data on WSU's location, as well as private repositories, which are a paid feature of Github.
So as far as our GitLab install goes, last night I looked into using a certificate from CACert. Turns out, to apply for a CACert you need to own the domain, so that was quickly scrapped. I don't think we can get HTTPS working at this point. I tried a few things with the configuration but it *seems* like the issue is the self-signed certificate and obtaining a legitimate certificate I don't think is possible. This isn't a huge issue, though with SSH you have to install keys on the server so it requires a bit more documentation.
What needs to be done with the server from here? I think all we need to do is resize the partition and virtual hard drive the server is on. I believe initially we set it to a 16gb install, but if students are going to use it for many assignments in their classes I feel like that'd fill up pretty quickly.
I missed a few things I wanted to go over with GitLab, and I have an update on trying out CACerts.I didn't really go over GitLab or git itself and why it's important.
To understand GitLab, first you have to understand git. Git is a revision control software for plain text files. What this means is, you edit the code, commit your changes, and edit it again, and your code changes are tracked. Linus Torvalds, the creator of the Linux kernel created it when he wasn't happy with the other software that was available. Git is one of my personal favourite tools to use, and has helped me with development a ton. I've definitely made poor choices in improving code or deleting code I didn't like and want to undo that- with proper use of git this is trivial. One really advantageous feature of git is that it's decentralized- when you clone a project with git, all its contents are self contained on your computer and if you want to update with a remote server you can pull the changes from the server or push your changes to the server. You can even have multiple remote repositories to push and pull from, though in practice you won't use that feature too much. Another useful feature is you can set the remote repository to be another location on your local machine- this can be useful if you're away from the internet and worried about accidentally ruining your working directory.
GitLab is probably the best free software alternative to Github. Github is a web front-end for remote git repositories, bring a lot of additional features to git such as editing your code from the web, forking other projects and pushing changes back to main projects (useful for feature development), easy account and group management, and of course the advantage of keeping your code stored on a remote server in case of issues with your local machine. For an example of a Github project, you can check out the CS-401 project from Spring 2013 that I was a member of. GitLab offers pretty much all of Github's main features and a familiar interface. The big advantage of GitLab over Github is that we can store the data on WSU's location, as well as private repositories, which are a paid feature of Github.
So as far as our GitLab install goes, last night I looked into using a certificate from CACert. Turns out, to apply for a CACert you need to own the domain, so that was quickly scrapped. I don't think we can get HTTPS working at this point. I tried a few things with the configuration but it *seems* like the issue is the self-signed certificate and obtaining a legitimate certificate I don't think is possible. This isn't a huge issue, though with SSH you have to install keys on the server so it requires a bit more documentation.
What needs to be done with the server from here? I think all we need to do is resize the partition and virtual hard drive the server is on. I believe initially we set it to a 16gb install, but if students are going to use it for many assignments in their classes I feel like that'd fill up pretty quickly.
I didn't really go over GitLab or git itself and why it's important.
To understand GitLab, first you have to understand git. Git is a revision control software for plain text files. What this means is, you edit the code, commit your changes, and edit it again, and your code changes are tracked. Linus Torvalds, the creator of the Linux kernel created it when he wasn't happy with the other software that was available. Git is one of my personal favourite tools to use, and has helped me with development a ton. I've definitely made poor choices in improving code or deleting code I didn't like and want to undo that- with proper use of git this is trivial. One really advantageous feature of git is that it's decentralized- when you clone a project with git, all its contents are self contained on your computer and if you want to update with a remote server you can pull the changes from the server or push your changes to the server. You can even have multiple remote repositories to push and pull from, though in practice you won't use that feature too much. Another useful feature is you can set the remote repository to be another location on your local machine- this can be useful if you're away from the internet and worried about accidentally ruining your working directory.
GitLab is probably the best free software alternative to Github. Github is a web front-end for remote git repositories, bring a lot of additional features to git such as editing your code from the web, forking other projects and pushing changes back to main projects (useful for feature development), easy account and group management, and of course the advantage of keeping your code stored on a remote server in case of issues with your local machine. For an example of a Github project, you can check out the CS-401 project from Spring 2013 that I was a member of. GitLab offers pretty much all of Github's main features and a familiar interface. The big advantage of GitLab over Github is that we can store the data on WSU's location, as well as private repositories, which are a paid feature of Github.
So as far as our GitLab install goes, last night I looked into using a certificate from CACert. Turns out, to apply for a CACert you need to own the domain, so that was quickly scrapped. I don't think we can get HTTPS working at this point. I tried a few things with the configuration but it *seems* like the issue is the self-signed certificate and obtaining a legitimate certificate I don't think is possible. This isn't a huge issue, though with SSH you have to install keys on the server so it requires a bit more documentation.
What needs to be done with the server from here? I think all we need to do is resize the partition and virtual hard drive the server is on. I believe initially we set it to a 16gb install, but if students are going to use it for many assignments in their classes I feel like that'd fill up pretty quickly.
by Jillur Rahman
Jillur Rahman is a Web designers. He enjoys to make blogger templates. He always try to make modern and 3D looking Templates. You can by his templates from Themeforest.
Follow him @ Twitter | Facebook | Google Plus
No Comment