gitlabhq / gitlab-recipes Goto Github PK
View Code? Open in Web Editor NEWMostly unofficial GitLab recipes for setup on different platforms, update etc...
License: Other
Mostly unofficial GitLab recipes for setup on different platforms, update etc...
License: Other
With git.createProject
when I create a project and set the option to True
either as a boolean or str(True)
in python I'm not able to get GitLab to actually create the project with the settings I want.
Still figuring it out.
The debian_ubuntu_aws.sh script runs fine on a fresh ubuntu EC2 instance using the AMI referenced, but when I try to access the web url I get a 502 error.
The troubleshooting command sudo -u gitlab bundle exec rake gitlab:app:status RAILS_ENV=production
returns this error :
Could not find pg-0.14.1 in any of the sources
Run bundle install to install missing gems.
After installing postgres and the missing gem:
sudo apt-get install postgresql
sudo gem install pg -v '0.14.1'
sudo bundle install
The error is now :
rake aborted!
Unknown database 'gitlabhq_production'
Indeed there are no tables in the mysql database, unicorn complains about this also.
Can someone help or point me in the right direction?
/etc/httpd/conf.d/gitlab.conf
Forbidden
You don't have permission to access /uploads/note/attachment/108/item_description.jpg on this server.
Apache/2.2.15 (CentOS) Server at git.example.com Port 80
## GitLab
<VirtualHost *:80>
ServerAdmin [email protected]
ServerName git.example.com
ProxyPass /uploads !
ProxyPass /error !
# Changed default 8080 to 9292 on unicorn.rb
# Timeout due to Building Graph (Still Failing)
ProxyPass / http://127.0.0.1:9292/ timeout=300
ProxyPassReverse / http://127.0.0.1:9292/ timeout=300
ProxyPreserveHost On
CustomLog /var/log/git_access.log combined
ErrorLog /var/log/git_error.log
DocumentRoot /home/git/gitlab/public
<Location />
Order allow,deny
Allow from all
</Location>
</VirtualHost>
[git@Example public]$ pwd
/home/git/gitlab/public
[git@Example public]$ ls -l
total 60
-rw-rw-r-- 1 git git 357 Aug 21 00:39 404.html
-rw-rw-r-- 1 git git 399 Aug 21 00:39 422.html
-rw-rw-r-- 1 git git 356 Aug 21 00:39 500.html
drwxrwxr-x 5 git git 8192 Sep 1 09:38 assets
-rw-rw-r-- 1 git git 374 Aug 21 00:39 deploy.html
-rw-rw-r-- 1 git git 1150 Aug 21 00:39 favicon.ico
-rw-rw-r-- 1 git git 17388 Aug 21 00:39 gitlab_logo.png
-rw-rw-r-- 1 git git 204 Aug 21 00:39 robots.txt
-rw-rw-r-- 1 git git 518 Aug 21 00:39 static.css
drwxrwxr-x 4 git git 4096 Sep 3 12:08 uploads
[git@Example gitlab]$ bundle exec rake gitlab:env:info RAILS_ENV=production && bundle exec rake gitlab:check RAILS_ENV=production
System information
System: CentOS release 6.4 (Final)
Current User: git
Using RVM: no
Ruby Version: 2.0.0p247
Gem Version: 2.0.3
Bundler Version:1.3.5
Rake Version: 10.1.0
GitLab information
Version: 6.1.0.pre
Revision: 54faf78
Directory: /home/git/gitlab
DB Adapter: mysql2
URL: http://git.example.com
HTTP Clone URL: http://git.example.com/some-project.git
SSH Clone URL: [email protected]:some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 1.7.1
Repositories: /home/git/repositories/
Hooks: /home/git/gitlab-shell/hooks/
Git: /usr/bin/git
Checking Environment ...
Git configured for git user? ... yes
Has python2? ... yes
python2 is supported version? ... yes
Checking Environment ... Finished
Checking GitLab Shell ...
GitLab Shell version >= 1.7.0 ? ... OK (1.7.1)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
update hook up-to-date? ... yes
update hooks in repos are links: ...
Group / Project ... ok
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Checking Sidekiq ... Finished
Checking GitLab ...
Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... no
Try fixing it:
Redownload the init script
For more information see:
doc/install/installation.md in section "Install Init Script"
Please fix the error above and rerun the checks.
Projects have satellites? ...
Group / Project ... yes
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (1.7.11)
Checking GitLab ... Finished
On guide to setup CentOS, item 5.1, you create a user "git" and try to test a user "gitlab".
https://github.com/gitlabhq/gitlab-recipes/blob/master/install/centos/README.md
Following the guide here - https://github.com/gitlabhq/gitlab-recipes/tree/master/install/centos
(centos 6.4 on rackspace cloud, mysql chosen instead of postgres for db)
I get up to the 'Install Gems' section and run:
bundle install --deployment --without development test postgres puma aws
And get the following:
Installing posix-spawn (0.3.6)
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.
/usr/local/bin/ruby extconf.rb
Gem files will remain installed in /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/posix-spawn-0.3.6 for inspection.
Results logged to /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/posix-spawn-0.3.6/ext/gem_make.out
An error occurred while installing posix-spawn (0.3.6), and Bundler cannot
continue.
Make sure that gem install posix-spawn -v '0.3.6'
succeeds before bundling.
I can successfully uninstall and install posix-spawn, but can not run the bundle install itself.
After much googling I'm still at a lost, any ideas?
On a fresh Ubuntu 12.04 system the following script gives an error:
sh: 1: /home/git/gitolite/src/gl-system-install: not found
sed: can't read /home/git/share/gitolite/conf/example.gitolite.rc: No such file or directory
sh: 1: gl-setup: not found
Steps to Reproduce:
Cause:
The expected folder does not exist
/home/git/gitolite/src/gl-system-install
Hi
I have been using the CentOS 6 install guide to try to install gitlab on my RHEL 6 system. I found it here:
https://github.com/gitlabhq/gitlab-recipes/blob/master/install/CentOS_6.md
It has some incorrect information. It says:
"During an installation on an official RHEL 6.3 we found that some packages (in our case gdbm-devel, libffi-devel and libicu-devel) were NOT installed. You MUST make sure that all the packages are installed. The simplest way is to run the above command for a second time and you'll see quite easily of everything is either already installed or "No package XXX available". When you run into this issue you can try installing these required packages from the CentOS distribution."
It's bad to install packages from CentOS on a RHEL server if you want to be in compliance with your subscription. You just need to add the rhel6 optional packages repo to your server to get those packages. Here's how you do it:
yum-config-manager --enable rhel-6-server-optional-rpms
That's it, then you can install libffi-devel libicu-devel gdbm-devel no problem.
Hi guys, thanks for the amazing scripts.
I ran the auto install script last night on a fresh ubuntu vm, It finished (or so I thought), but it had actually just stopped part way.
It would appear to have stopped on line 147, that section looks like:
sudo -u gitlab -H git clone https://github.com/gitlabhq/gitlabhq.git gitlab
cd /home/gitlab/gitlab
On my machines the git command checked out to /home/gitlab/gitlabhq, so the cd failed, which stopped the script.
I managed to finished off the instructions manually (after fixing the mysql root password I now had no idea of).
reopend here from gitlabhq (https://github.com/gitlabhq/gitlabhq/issues/1859)
apt-get install curl sudo
curl https://raw.github.com/gitlabhq/gitlab-recipes/master/install/debian_ubuntu.sh | sh
This command fails:
sudo -u gitlab -H git clone git@localhost:gitolite-admin.git /tmp/gitolite-admin
It requests for a password for the user git. I have no idea what the password it, in the entire process I was not asked to give one, and I could not find in the documentation any reason for this to fail.
May I suggest you to use openssl, a default installed command, instead makepasswd, which must be installed yet?
$ openssl rand -base64 16
zB5HFNcYHPs2DYWt4Bsdzw==
How can I make the notification mail services work on gitab 6.0 after fresh installation on centos?
Waiting for responses..
Regards..
I'm suggesting a feature enhancement in the ubuntu recipe installer to not use source code build and use rvm instead.
Hi!
I have done this for my installation and would like to share and ask for advise.
The file is /etc/logrotate.d/gitlab and has the following content:
/home/gitlab/gitlab/log/application.log
/home/gitlab/gitlab/log/development.log
/home/gitlab/gitlab/log/githost.log
/home/gitlab/gitlab/log/production.log
/home/gitlab/gitlab/log/sidekiq.log
/home/gitlab/gitlab/log/unicorn.stderr.log
/home/gitlab/gitlab/log/unicorn.stdout.log
{
rotate 7
daily
maxsize 10M
minsize 1M
missingok
notifempty
compress
delaycompress
sharedscripts
postrotate
invoke-rc.d gitlab restart > /dev/null
endscript
}
The tricky part is the restart, because the reload wasn't enough to make the running processes close and reopen the log files. This works well and the logs rotate as intended.
Logrotate runs daily by crontab. And I noticed that the message queues were left in unusable state after restart, so the email notifications stopped.
I found that stopping and starting sidekiq was enough to get it working again and then I went looking for the cause in the init.d script. It seems that running stop and start operations for sidekiq as background processes caused some kind of race condition.
So to fix this I removed the trailing '&' from the commands in lines 77 and 79:
...
sudo -u gitlab -H bash -l -c "mkdir -p $PID_PATH && $STOP_SIDEKIQ > /dev/null 2>&1 &"
....
sudo -u gitlab -H bash -l -c "mkdir -p $PID_PATH && $START_SIDEKIQ > /dev/null 2>&1 &"
...
Could anyone check if this problem can safely be fixed this way?
== Seed from /home/git/gitlab/db/fixtures/production/001_admin.rb
rake aborted!
undefined method `avatar_changed?' for #<User:0x007f62799b7c28>
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:46:in `eval'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/attribute_methods.rb:155:in `method_missing'
/home/git/gitlab/app/models/user.rb:118:in `block in <class:User>'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/callbacks.rb:753:in `_run__4385683779128637065__validate__callbacks'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/callbacks.rb:80:in `run_callbacks'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activemodel-4.0.2/lib/active_model/validations.rb:373:in `run_validations!'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activemodel-4.0.2/lib/active_model/validations/callbacks.rb:106:in `block in run_validations!'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/callbacks.rb:414:in `block in _run__4385683779128637065__validation__callbacks'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/callbacks.rb:212:in `block in _conditional_callback_around_120'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_model.rb:514:in `block in around_validation'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:150:in `block in run_actions'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:170:in `catch_exceptions'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:148:in `run_actions'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:133:in `run_callbacks'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:212:in `run_callbacks'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:63:in `block (2 levels) in perform'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:63:in `catch'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:63:in `block in perform'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:186:in `within_transaction'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:62:in `perform'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_model.rb:514:in `around_validation'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/callbacks.rb:283:in `_callback_around_99'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/callbacks.rb:211:in `_conditional_callback_around_120'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/callbacks.rb:373:in `_run__4385683779128637065__validation__callbacks'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/callbacks.rb:80:in `run_callbacks'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activemodel-4.0.2/lib/active_model/validations/callbacks.rb:106:in `run_validations!'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activemodel-4.0.2/lib/active_model/validations.rb:314:in `valid?'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/validations.rb:70:in `valid?'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/validations.rb:77:in `perform_validations'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/validations.rb:51:in `save'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/attribute_methods/dirty.rb:32:in `save'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/transactions.rb:270:in `block (2 levels) in save'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/transactions.rb:326:in `block in with_transaction_returning_status'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/abstract/database_statements.rb:200:in `transaction'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/transactions.rb:209:in `transaction'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/transactions.rb:323:in `with_transaction_returning_status'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/transactions.rb:270:in `block in save'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/transactions.rb:281:in `rollback_active_record_state!'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/transactions.rb:269:in `save'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:483:in `block in save'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:502:in `block (2 levels) in around_save'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:150:in `block in run_actions'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:170:in `catch_exceptions'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:148:in `run_actions'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:133:in `run_callbacks'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:212:in `run_callbacks'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:63:in `block (2 levels) in perform'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:63:in `catch'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:63:in `block in perform'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:186:in `within_transaction'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:62:in `perform'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:502:in `block in around_save'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:530:in `block in transaction'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/abstract/database_statements.rb:200:in `transaction'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/transactions.rb:209:in `transaction'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:529:in `transaction'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:501:in `around_save'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:483:in `save'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/protected_attributes-1.0.5/lib/active_record/mass_assignment_security/persistence.rb:46:in `create'
(eval):1:in `block (2 levels) in run_file'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:46:in `eval'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:46:in `block (2 levels) in run_file'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:58:in `block in open'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:57:in `open'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:57:in `open'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:36:in `block in run_file'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/abstract/database_statements.rb:202:in `block in transaction'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/abstract/database_statements.rb:210:in `within_new_transaction'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/abstract/database_statements.rb:202:in `transaction'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/transactions.rb:209:in `transaction'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:35:in `run_file'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:26:in `block in run'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:25:in `each'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:25:in `run'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/seed-fu-2.3.0/lib/seed-fu.rb:29:in `seed'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/seed-fu-2.3.0/lib/tasks/seed_fu.rake:36:in `block (2 levels) in <top (required)>'
/home/git/gitlab/lib/tasks/gitlab/setup.rake:18:in `setup_db'
/home/git/gitlab/lib/tasks/gitlab/setup.rake:4:in `block (2 levels) in <top (required)>'
Tasks: TOP => db:seed_fu
(See full trace by running task with --trace)
After running
sudo -u git -H bundle exec rake gitlab:setup RAILS_ENV=production
It looks like it's tied to https://github.com/gitlabhq/gitlabhq/blob/master/app/models/user.rb#L118
Is there a known quick fix for this issue?
System information
System: CentOS release 6.4 (Final)
Current User: git
Using RVM: no
Ruby Version: 2.0.0p247
Gem Version: 2.0.3
Bundler Version:1.3.5
Rake Version: 10.1.0
GitLab information
Version: 6.0.0
Revision: 4c8f369
Directory: /home/git/gitlab
DB Adapter: mysql2
URL: http://git.mydomain.com
HTTP Clone URL: http://git.mydomain.com/some-project.git
SSH Clone URL: [email protected]:some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 1.7.0
Repositories: /home/git/repositories/
Hooks: /home/git/gitlab-shell/hooks/
Git: /usr/local/bin/git
git@server [/gitlab]# exit]# service gitlab start
logout
root@server [
Starting unicorn: [ OK ]
Starting sidekiq: [ OK ]
After enabled auto-start of gitlab via the gitlab script, unicorn process failed to start at boot because redis wasn't loaded yet. I tried to load the gitlab service via shell without problems, so I suspected that something was wrong with the load order of these services at boot.
I managed to fix this by renaming the symlink S20gitlab to S30gitlab in /etc/rc2.d (Ubuntu 12.04) so, by leaving the S20redis-server symlink, the redis server gets loaded before the gitlab service, fixing the issue.
Unfortunately I don't know where to change this in code, but i suspect that the gitlab recipe is involved. Hope someone can fix it definitely
i am installing gitlab on my ubuntu 12.04.2 server , i ran the ubuntu_server_1204.sh script for installing, it promots the error information when it is installing ruby,
error information:
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... configure: error: in /home/plc/ruby-1.9.3-p327': configure: error: cannot run C compiled programs. If you meant to cross compile, use
--host'.
See `config.log' for more details
so how can i fix it
Finally after so many hours trying to setup GitLab-4-0 on our local server I managed to get it working on Centos 6.3.
Unfortunately, not everything is 100%. The /etc/init.d/ that I got from https://raw.github.com/gitlabhq/gitlab-recipes/4-0-stable/init.d/gitlab doesn't really work.
when I run sudo service gitlab start resque starts fine, unicorn doesn't.
Starting unicorn: bash: bundle: command not found
[FAILED]
Starting resque: [ OK ]
I have to switch to gitlab user, cd into /home/gitlab/gitlab and manually start unicorn:
bundle exec unicorn_rails -c config/unicorn.rb -E production -D
Once unicorn is running I can sudo service gitlab start
[gitlab@devserver gitlab]$ sudo service gitlab start
Starting unicorn:
Starting resque: [ OK ]
The problem with this is that if my server restarts for whatever reason, I have to manually do it all over again.
Anyone know why Starting unicorn: bash: bundle: command not found is happening?
I'm using rvm to manage ruby versions and version is 1.9.3-p385, ruby is on my path.
The installation hangs on a CentOS 6.5 system, because the assets aren't precompiled, after install you need to run:
bundle exec rake assets:precompile RAILS_ENV=production
I ran up to the step: https://github.com/gitlabhq/gitlab-recipes/tree/master/install/centos#start-your-gitlab-instance
Then:
service gitlab start
Starting unicorn:ERROR: RVM Ruby not used, run `rvm use ruby` first.
[FAILED]
Starting sidekiq: ERROR: RVM Ruby not used, run `rvm use ruby` first.
[FAILED]
But (Ruby install via rvm.)
ruby -v
ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-linux]
bundle exec rake gitlab:env:info RAILS_ENV=production
System information
System: CentOS release 6.4 (Final)
Current User: git
Using RVM: yes
RVM Version: 1.22.3
Ruby Version: 2.0.0p247
Gem Version: 2.0.3
Bundler Version:1.3.5
Rake Version: 10.1.0
Hi,
I've found that the ini.t/gitlab code here has some problems when you restart it, since resque process remains Paused forever.
The modified code described here works well:
https://gist.github.com/abevoelker/gitlabhq/blob/stable/doc/installation.md
After succesfully updating gitlab from 4.0.1 to 4.1 as described, I can't access gitlab from port 80 by introducing the recipe provided here anymore.
Port 80 responses with
Not Found: /
Port 3000 is working normal.
Please note, I needed to install redis 2.4 from backports (as descriped here: gitlabhq/gitlabhq#2675) to get gitlab 4.1 work on squeeze correctly.
#service gitlab start
Starting the GitLab Unicorn web server...
/usr/bin/env: ruby: No such file or directory
Starting the GitLab Sidekiq event dispatcher...
/usr/bin/env: ruby: No such file or directory
# bundle exec rake gitlab:env:info RAILS_ENV=production
Could not locate Gemfile
[git gitlab]$ bundle exec rake gitlab:env:info RAILS_ENV=production
System information
System: CentOS release 6.4 (Final)
Current User: git
Using RVM: no
Ruby Version: 2.0.0p247
Gem Version: 2.0.3
Bundler Version:1.3.5
Rake Version: 10.1.0
GitLab information
Version: 6.0.2
Revision: 10b0b8f
Directory: /home/git/gitlab
DB Adapter: mysql2
URL: http://git.example.com
HTTP Clone URL: http://git.example.com/some-project.git
I am following the install guide at https://github.com/gitlabhq/gitlab-recipes/tree/master/install/centos
Running into the following problem and couldn't find a resolution doing a google search...
root@gitlab gitlab]# bundle exec rake gitlab:setup RAILS_ENV=production
rake aborted!
Specified 'postgresql' for database adapter, but the gem is not loaded. Add gem 'pg'
to your Gemfile.
Tasks: TOP => gitlab:setup => environment
(See full trace by running task with --trace)
[root@gitlab gitlab]#
Here's part of my Gemfile.....
ource "https://rubygems.org"
def darwin_only(require_as)
RUBY_PLATFORM.include?('darwin') && require_as
end
def linux_only(require_as)
RUBY_PLATFORM.include?('linux') && require_as
end
gem "rails", "~> 4.0.0"
gem "protected_attributes"
gem 'rails-observers'
gem 'actionpack-page_caching'
gem 'actionpack-action_caching'
gem 'activerecord-deprecated_finders'
gem "mysql2", group: :mysql
gem "pg", group: :postgres
I followed all the steps up to this point from the install guide...
What's the fix?
I have a github repo that provides:
It will soon provide:
Can this be linked to on gitlab-recipes? It didn't seem like it belonged as a direct fork since there will be a lot of other commits related to the packages and backup functionality.
My repository:
https://github.com/mhathcock/gitlab-ubuntu
On running sudo service gitlab start the following processes start up:
git 2507 24.3 0.6 918716 110576 pts/5 Sl 21:44 0:19 unicorn_rails master -c /home/git/gitlab/config/unicorn.rb -E production
git 2577 0.1 0.0 50860 10468 pts/5 S 21:44 0:00 python2 /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/gitlab-pygments.rb-0.3.2/lib/pygments/mentos.py
git 2594 26.0 0.6 3070944 114068 pts/5 Sl 21:44 0:18 sidekiq 2.7.5 gitlab [0 of 25 busy]
git 2618 0.1 0.0 49400 10412 pts/5 S 21:44 0:00 python2 /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/gitlab-pygments.rb-0.3.2/lib/pygments/mentos.py
git 2628 0.0 0.6 919376 104624 pts/5 Sl 21:44 0:00 unicorn_rails worker[0] -c /home/git/gitlab/config/unicorn.rb -E production
git 2634 0.0 0.6 919376 104600 pts/5 Sl 21:44 0:00 unicorn_rails worker[1] -c /home/git/gitlab/config/unicorn.rb -E production
postgres 2646 0.0 0.0 128376 6376 ? Ss 21:44 0:00 postgres: gitlab gitlabhq_production [local] idle
After that, if the service is stopped and started in quick succession a few times, (More specifically on quick repetitions of sudo service gitlab restart) from then on a subset of the processes listed above seem to keep on running forever unless manually terminated.
This problem seems to get in the way mainly when testing out various configurations of the gitlab server ie,. in the case when quick reloads of the gitlab server are required.
Would be nice if there was a systemd unit file (for us arch users) along with the init.d script.
If nobody else takes a swing at it, when I get a chance I'll give it a shot. Would be nice too considering that systemd would allow for starting gitlab once redis/resque are up (the proper dependency startup is quite nice)
Hello,
I used a modified script to install gitlab 5.4 on RHEL 6.3. I was initially using this command to download the init script:
curl --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlab-recipes/master/init.d/gitlab-centos
but looking around here it seems the init script URL has changed.
However, even after making the change, I still get this error:
service gitlab status
/etc/init.d/gitlab: line 1: syntax error near unexpected token `newline'
/etc/init.d/gitlab: line 1: `<!DOCTYPE html>'
The script shouldn't be an HTML file but it seems like that's the case for me. Has the URL been updated again? I get a 404 error when I access it via the browser.
Any help would be appreciated.
Thanks.
My server is running CentOS 6.4, I've installed gitlab 5.3 according to this instruction
https://github.com/gitlabhq/gitlab-recipes/blob/master/install/CentOS_6.md
The init script is also the latest version
https://raw.github.com/gitlabhq/gitlabhq/5-3-stable/lib/support/init.d/gitlab
All checks run OK, but when I attempt to start gitlab service, it doesn't actually start(
http://d.pr/i/Ope5
The uploads should not be served through the proxy.
#serve the uploads without proxy
ProxyPass /uploads !
Could anyone with a strong modsec2 background get with others to collaborate on useful modsec2 custom rules for both whitelisting and 500 denies with audit logging?
The current AWS installation script fails to make a working setup. Adding the libpq-dev package fixes the problem.
@axilleas I have a question for you. I'd like to contribute best practice documentation which can be used in RHEL.
https://github.com/gitlabhq/gitlab-recipes/tree/master/install/centos
There is already CentOS documentation but my idea of an install and the steps to go about it are considerably different for a production RHEL install than what that guide covers.
Should I contribute a separate document for RHEL or should I completely revamp the CentOS documentation?
Took me all night to track this down as it wasn't giving me errors or anything.
In the config/unicorn.rb had to change:
working_directory "/home/git/gitlab/current"
to
working_directory "/home/git/gitlab"
After following the guide at this link "gitlab-recipes/install/v4" I still couldn't get gitlab up and running. The ps command showed no nginx process and I don't know where to look for the installation log.
Could you guy please provide a link to a Vagrant box that contains gitlab v4 setup. It would help other people a lot.
P/S: This is my 5th tries with gitlab and still couldn't get it working. I know this is a very promising project but the installation is just complicated as hell. As an user I just need a VM image to get gitlab up and running instantly.
Thanks.
Just a reminder.
the Readme page for the ubuntu points a wrong location of the installation script.
Current:
Run script (replace gitlab.example.com with your domain or ip address)
curl https://raw.github.com/gitlabhq/gitlab-recipes/master/install/v4/ubuntu_server_1204.sh | sudo domain_var=gitlab.example.com sh
Reboot machine
Correct:
https://raw.github.com/gitlabhq/gitlab-recipes/master/install/ubuntu/ubuntu_server_1204.sh
bundle exec rake gitlab:env:info RAILS_ENV=production
Result:
Init script up-to-date? ... no
Try fixing it:
Redownload the init script
For more information see:
doc/install/installation.md in section "Install Init Script"
Please fix the error above and rerun the checks.
I change init script by #121 (comment)
/usr/local/lib/ruby/gems/1.9.1/gems/octokit-2.7.1/lib/octokit/error.rb:44:in `[]': can't convert Symbol into Integer (TypeError)
from /usr/local/lib/ruby/gems/1.9.1/gems/octokit-2.7.1/lib/octokit/error.rb:44:in `documentation_url'
from /usr/local/lib/ruby/gems/1.9.1/gems/octokit-2.7.1/lib/octokit/error.rb:130:in `build_error_message'
from /usr/local/lib/ruby/gems/1.9.1/gems/octokit-2.7.1/lib/octokit/error.rb:37:in `initialize'
from /usr/local/lib/ruby/gems/1.9.1/gems/octokit-2.7.1/lib/octokit/error.rb:31:in `new'
from /usr/local/lib/ruby/gems/1.9.1/gems/octokit-2.7.1/lib/octokit/error.rb:31:in `from_response'
from /usr/local/lib/ruby/gems/1.9.1/gems/octokit-2.7.1/lib/octokit/response/raise_error.rb:15:in `on_complete'
from /usr/local/lib/ruby/gems/1.9.1/gems/faraday-0.9.0/lib/faraday/response.rb:9:in `block in call'
from /usr/local/lib/ruby/gems/1.9.1/gems/faraday-0.9.0/lib/faraday/response.rb:57:in `on_complete'
from /usr/local/lib/ruby/gems/1.9.1/gems/faraday-0.9.0/lib/faraday/response.rb:8:in `call'
from /usr/local/lib/ruby/gems/1.9.1/gems/faraday-0.9.0/lib/faraday/rack_builder.rb:139:in `build_response'
from /usr/local/lib/ruby/gems/1.9.1/gems/faraday-0.9.0/lib/faraday/connection.rb:377:in `run_request'
from /usr/local/lib/ruby/gems/1.9.1/gems/faraday-0.9.0/lib/faraday/connection.rb:140:in `get'
from /usr/local/lib/ruby/gems/1.9.1/gems/sawyer-0.5.3/lib/sawyer/agent.rb:94:in `call'
from /usr/local/lib/ruby/gems/1.9.1/gems/octokit-2.7.1/lib/octokit/client.rb:257:in `request'
from /usr/local/lib/ruby/gems/1.9.1/gems/octokit-2.7.1/lib/octokit/client.rb:194:in `paginate'
from /usr/local/lib/ruby/gems/1.9.1/gems/octokit-2.7.1/lib/octokit/client/repositories.rb:63:in `repositories'
from import_all.rb:71:in `<main>'
I was installing Gitlab on my CentOS 6.4 server, following the manual. All the setups went well, and the bundle exec rake gitlab:check RAILS_ENV=production
produced everything's ok output. But, for some reason, when I first tried visit my server, I got Error 500. I checked the production.log
and that's what I saw:
Connecting to database specified by database.yml
Started GET "/" for 195.160.253.4 at 2013-07-30 10:13:50 +0400
Processing by DashboardController#show as HTML
Completed 401 Unauthorized in 1ms
Started GET "/users/sign_in" for 195.160.253.4 at 2013-07-30 10:13:51 +0400
Processing by Devise::SessionsController#new as HTML
Completed 500 Internal Server Error in 21ms
ActiveRecord::StatementInvalid (Mysql2::Error: Table 'gitlabhq_production.users' doesn't exist: SHOW FULL FIELDS FROM `users`):
config/initializers/connection_fix.rb:22:in `execute'
Looks like not the all tables were created. I ckecked my guess:
mysql> SHOW TABLES;
+-------------------------------+
| Tables_in_gitlabhq_production |
+-------------------------------+
| deploy_keys_projects |
| events |
| forked_project_links |
| issues |
| keys |
| merge_requests |
| milestones |
| namespaces |
| notes |
| projects |
| protected_branches |
| services |
| snippets |
| taggings |
+-------------------------------+
14 rows in set (0.00 sec)
After some investigation I ran bundle exec rake db:migrate RAILS_ENV=production
, and the error is gone.
I don't know whether it is a missed step in the installation guide or a Gitlab bug, so I am informing you.
EDIT
Yep, it is a missed step in install guide.
Starting puma: /usr/lib/ruby/site_ruby/1.8/rubygems.rb:805:in report_activate_error': Could not find RubyGem bundler (>= 0) (Gem::LoadError) from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:243:in
activate'
from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:50:in gem' from /usr/bin/bundle:18 [FAILED] Starting sidekiq: /usr/lib/ruby/site_ruby/1.8/rubygems.rb:805:in
report_activate_error': Could not find RubyGem bundler (>= 0) (Gem::LoadError)
from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:243:in activate' from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:50:in
gem'
from /usr/bin/bundle:18
[FAILED]
ANy ideas?
its the init.d-script here for centos doesn't work with gitlabhq/gitlabhq@2c0f4c7
Hello,
I have installed Gitlab6.0 on CentOS6.3 according to instruction https://github.com/gitlabhq/gitlab-recipes/tree/master/install/centos
My Gitlab is running on apache with unicorn.
Almost everything seems to work fine, but in "New Team member(s)" page, drop-down menu to choose member doesn't appear,
also in "Group members" page, I can't see drop-down menu.
When click [New team member], Here is what I got in gitlab/log/production.log
Started GET "/msaito/td-agent_test/team_members/new" for xx.xx.xx.xx at 2013-10-04 08:55:41 +0900
Processing by Projects::TeamMembersController#new as HTML
Parameters: {"project_id"=>"msaito/td-agent_test"}
Rendered projects/team_members/form.html.haml (2.0ms)
Rendered projects/teammembers/new.html.haml within layouts/project_settings (2.4ms)
Rendered layouts/head.html.haml (1.2ms)
Rendered layouts/search.html.haml (14.9ms)
Rendered layouts/headpanel.html.haml (20.8ms)
Rendered layouts/initauto_complete.html.haml (5.3ms)
Rendered layouts/flash.html.haml (0.1ms)
Rendered shared/no_ssh.html.haml (1.1ms)
Rendered layouts/nav/project.html.haml (9.6ms)
Rendered projects/settings_nav.html.haml (1.9ms)
Completed 200 OK in 71ms (Views: 42.8ms | ActiveRecord: 4.2ms)
Started GET "/assets/logo-black.png" for xx.xx.xx.xx at 2013-10-04 08:55:42 +0900
Started GET "/assets/icon-search.png" for xx.xx.xx.xx at 2013-10-04 08:55:42 +0900
Served asset /icon-search.png - 304 Not Modified (0ms)
any help would be appreciate.
please add daemon script for gitlab_ci
I got a complete install on CentOS up and working with the help of the guide, and I can access almost every page through the portal. But whenever I click Admin Area I get this error:
Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Apache/2.2.15 (CentOS) Server at redactedservername.redactedcompany.vci Port 80
I am unable to add keys for people to access the repo without being able to access this page right? I'm new to this GitLab thing. If you need more info let me know. There was nothing alarming in any of the logs in gitlab/log/ so I don't know what could be happening. Literally this is all I'm getting in production.log
Started GET "/favicon.ico" for 127.0.0.1 at 2013-08-16 03:35:07 +0000
Processing by ProjectsController#show as */*
Parameters: {"id"=>"favicon.ico"}
Rendered public/404.html (0.1ms)
Filter chain halted as :project rendered or redirected
Completed 404 Not Found in 5ms (Views: 0.9ms | ActiveRecord: 0.9ms)
puma-2.0.0.b7/lib/puma/cli.rb:337:in `parse_options': invalid option: -E (OptionParser::InvalidOption)
-E option for Puma is not valid :(
I am trying to install Gitlab to CentOS v. 6.4.
I can't find a correct init file. I've tried those:
Every time I run bundle exec rake gitlab:check RAILS_ENV=production
I get following:
Init script up-to-date? ... no
Try fixing it:
Redownload the init script
For more information see:
doc/install/installation.md in section "Install Init Script"
Please fix the error above and rerun the checks.
BTW URL in install guide is broken.
[git@Gid-server gitlab]$ bundle exec rake gitlab:setup RAILS_ENV=production
rake aborted!
Specified 'postgresql' for database adapter, but the gem is not loaded. Add `gem 'pg'` to your Gemfile.
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/connection_specification.rb:58:in `rescue in resolve_hash_connection'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/connection_specification.rb:55:in `resolve_hash_connection'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/connection_specification.rb:46:in `resolve_string_connection'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/connection_specification.rb:30:in `spec'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/connection_handling.rb:39:in `establish_connection'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/railtie.rb:176:in `block (2 levels) in <class:Railtie>'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/lazy_load_hooks.rb:38:in `instance_eval'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/lazy_load_hooks.rb:38:in `execute_hook'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/lazy_load_hooks.rb:28:in `block in on_load'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/lazy_load_hooks.rb:27:in `each'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/lazy_load_hooks.rb:27:in `on_load'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activerecord-4.0.2/lib/active_record/railtie.rb:174:in `block in <class:Railtie>'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/railties-4.0.2/lib/rails/initializable.rb:30:in `instance_exec'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/railties-4.0.2/lib/rails/initializable.rb:30:in `run'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/railties-4.0.2/lib/rails/initializable.rb:55:in `block in run_initializers'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/railties-4.0.2/lib/rails/initializable.rb:54:in `run_initializers'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/railties-4.0.2/lib/rails/application.rb:215:in `initialize!'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/railties-4.0.2/lib/rails/railtie/configurable.rb:30:in `method_missing'
/home/git/gitlab/config/environment.rb:5:in `<top (required)>'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/railties-4.0.2/lib/rails/application.rb:189:in `require_environment!'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/railties-4.0.2/lib/rails/application.rb:250:in `block in run_tasks_blocks'
Tasks: TOP => gitlab:setup => environment
(See full trace by running task with --trace)
[git@Gid-server gitlab]$ find postgresql
find: `postgresql': No such file or directory
How to fix it?
The configuration file for apache given causes uploads to return a 502 Proxy Error.
To do this, gitlab noly checks if the file '/etc/init.d/gitlab' is same with 'lib/support/init.d/gitlab"'. This is right when we use ubuntu. When we install gitlab on CentOS, we download the file from https://github.com/gitlabhq/gitlab-recipes/tree/master/init/sysvinit/centos/gitlab-unicorn, so it is not same with 'lib/support/init.d/gitlab', then the command 'bundle exec rake gitlab:check RAILS_ENV=production' said '/etc/init.d/gitlab' is not up-to-date.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.