New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non interactive aws install #1318
Non interactive aws install #1318
Conversation
|
|
@randx Squashed into one commit and moved into aws dir. |
|
How about |
|
@randx Let me know what I can do to get this in. I'll be glad to change the directory to /doc/aws or to multiple dirs (/lib/support/aws & /lib/support/nginx) |
|
@dosire Oh sorry. Forget about. Lets do next:
|
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.
|
@randx I've moved the files under lib/support/aws as you requested. I've rebased so you should be able to merge via the ui, let me know if this is not the case. In addition I've incorporated the latest changes in installation.md and now use the predefined init files you added 5 days ago. |
Merge branch 'master' into non-interactive-aws-install Conflicts: doc/installation.md Fix merge mess in installation.md
Conflicts: doc/installation.md
Non interactive aws install
Git 2 docs Related to #1318
The current installation manual is very well written. But it is still a bit of work to set up a new server.
To offer an alternative to people wanting to try out Gitlab quickly I made a script that does a complete installation on Amazon Web Services. After pasting one line in the server the next step is to log in to a running server that is properly configured (push/pull/email/resque/etc.).
The TODO's as listed in the script are:
On the first on I would like your input.
For he second one I will send a merge request when the this one is merged in.
This is quite a bit of code so please let me know if you prefer changes, I have no problem with changing things.