330fe4162e
There was an error in the #extract_attributes_from_page method that caused an exception when checking to see if a page named "Home" already exists. The check occurs to handle the renaming of the main index page to "Home" to match the Gollum standard. If there is already a page called "Home" then the migrator will leave that page and create the Index page as usual. Users will need to manually rename their old "Home" page to something else then rename their "Index" page to "Home". Fortunately, I would be highly surprised if this case ever comes up. I also added more verbosity to the logging so if an error does occur, it will be easier to track down which Wiki page is causing the problem. |
||
|---|---|---|
| app | ||
| config | ||
| db | ||
| doc | ||
| features | ||
| lib | ||
| log | ||
| public | ||
| script | ||
| spec | ||
| tmp | ||
| vendor | ||
| .foreman | ||
| .gitignore | ||
| .rspec | ||
| .simplecov | ||
| .travis.yml | ||
| CHANGELOG | ||
| CONTRIBUTING.md | ||
| Capfile.example | ||
| Gemfile | ||
| Gemfile.lock | ||
| Guardfile | ||
| LICENSE | ||
| Procfile | ||
| README.md | ||
| ROADMAP.md | ||
| Rakefile | ||
| VERSION | ||
| config.ru | ||
README.md
GitLab: self hosted Git management software
GitLab allows you to
- keep your code secure on your own server
- manage repositories, users and access permissions
- communicate through issues, line-comments and wiki pages
- perform code review with merge requests
GitLab is
- powered by Ruby on Rails
- completely free and open source (MIT license)
- used by 10.000 organizations to keep their code secure
Code status
-
ci.gitlab.org (master branch)
-
travis-ci.org (master branch) -
-
-
Resources
-
GitLab.org community site: Homepage Screenshots Blog Demo
-
GitLab.com commercial services: Homepage GitLab Cloud Subscription Consultancy Blog
-
GitLab CI: Readme of the GitLab open-source continuous integration server
Requirements
- Ubuntu/Debian**
- ruby 1.9.3
- MySQL
- git
- gitlab-shell
- redis
** More details are in the requirements doc
Installation
For production
Follow the installation guide for production server.
-
Installation guide for latest stable release (4.2) - Recommended
For development
If you want to contribute, please first read our Contributing Guidelines and then we suggest you to use the Vagrant virtual machine project to get an environment working sandboxed and with all dependencies.
Starting
-
The Installation guide contains instructions to download an init script and run that on boot. With the init script you can also start GitLab
sudo service gitlab start
or
sudo /etc/init.d/gitlab restart
-
Start it with Foreman in development mode
bundle exec foreman start -p 3000
or start it manually
bundle exec rails s
bundle exec rake sidekiq:start
Running the tests
-
Seed the database
bundle exec rake db:setup RAILS_ENV=test bundle exec rake db:seed_fu RAILS_ENV=test -
Run all tests
bundle exec rake gitlab:test -
Rspec unit and functional tests
bundle exec rake spec -
Spinach integration tests
bundle exec rake spinach
Getting help
New versions and the API
Each month on the 22th a new version is released together with an upgrade guide.