02 Sep, 2012
1 commit
-
Non-interactive AWS install by running a single script. Complete non-interactive AWS install with one line. Squash of 28 commits: Initial commit of complete install script. Must be sudo. Non interactive prostgres. Install mysql with unique password. Service file. Add init file. Nginx config. Script contains aws specific settings. Update references after rename. Prevent localhost ssh prompt. Postfix with policyd. Typo in localhost. Postfix package has other name. sudo -l session needs oneliners. More sudo commands to prevent permission problems. Change in existing file. Change in existing file must be referenced. Switch order. Postfix comment. Old way to generate password, less sudo. todo login Must use private ip and login instructions. Starting up. Fixed and checked various todos. Use service. Set host name. Go to default dir. Only works on next login. Only replace first host. Cleaned up the comments. Link to nginx config. Move to aws dir. Update links to aws for interactive install. Existing script stays at the same location. Change directory. Use the new init scripts for gitlab service and nginx. Use the branch for file downloads. Update with newest changes to installation.md. Correct reference. Use master branch since we need the nginx condfig and use absolute paths. Need to copy with sudo.
19 Aug, 2012
2 commits
17 Aug, 2012
1 commit
16 Aug, 2012
1 commit
14 Aug, 2012
1 commit
13 Aug, 2012
2 commits
10 Aug, 2012
1 commit
-
Didn't bother with files in db/, config/, or features/
06 Aug, 2012
1 commit
03 Aug, 2012
1 commit
-
Fix UMASK checking in .gitoliterc
02 Aug, 2012
1 commit
01 Aug, 2012
3 commits
31 Jul, 2012
1 commit
27 Jul, 2012
2 commits
26 Jul, 2012
3 commits
-
Potential solution for current `rake gitlab:app:backup_restore` issues.
-
…ore repositories based on their `path` rather than their (project) `name`. The project name can be uppercase and may contain spaces. This caused the repository to be restored as a different `path` that it was initially created as, thus, breaking the `git remote` and the web interface can no longer detect the repository either because it searches by `path` and not by `name`. Also, when restoring the permissions are incorrect making it impossible to push new commits to the remote repository. So now on success it'll set the correct permissions (but requires that the `gitlab` user has `sudo` privileges, or this task must be executed as root).
25 Jul, 2012
5 commits
-
Create the githost.log file if necessary.
24 Jul, 2012
2 commits
21 Jul, 2012
1 commit
-
This resolves issue #1121. Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>
18 Jul, 2012
1 commit
17 Jul, 2012
1 commit
16 Jul, 2012
1 commit
10 Jul, 2012
2 commits
06 Jul, 2012
1 commit
05 Jul, 2012
4 commits
04 Jul, 2012
1 commit
-
Inline diff