-
Notifications
You must be signed in to change notification settings - Fork 53
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
Readme update for remote install #40
Conversation
README.md
Outdated
1. SSH into your remote server and add an `ubuntu` [user with sudo privileges](https://www.digitalocean.com/community/tutorials/how-to-create-a-sudo-user-on-ubuntu-quickstart) | ||
1. Clone the repository onto your local machine | ||
1. Create an inventory for your new environment ('production' in this example): `cp -r inventory/vagrant inventory/production` | ||
1. Edit `inventory/produciont/hosts` to point to your new environment by changing 'default' line to: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo produciont
Made a PR on the PR here: dannylamb#1 |
@dannylamb The instructions do not say if an ubuntu user is needed in the target machine. Is it needed? May have to merge with this: #11 |
@Natkeeran As far as I can tell, yes. I tried with and without an ubuntu user and it totally flopped wihtout it. What I'm not sure of is if we can get away with any user that has sudo privileges, or if it must be named |
I think after my PR it can be any user with sudo privileges, but I have to go give it a try to make sure. |
@dannylamb @jonathangreen |
daniel@daniel-Latitude-3560:~/Code/Environments/claw-playbook$ grep -rn "/home/ubuntu" .
./roles/internal/webserver-app/defaults/main.yml:7:webserver_app_jwt_key_path: /home/ubuntu/auth
./roles/internal/webserver-app/defaults/main.yml:8:webserver_app_jwt_config_path: /home/ubuntu/configs/jwt
./roles/internal/webserver-app/defaults/main.yml:10:webserver_app_drupal_config_path: /home/ubuntu/configs/drupal
./.vagrant/machines/default/virtualbox/synced_folders:1:{"virtualbox":{"/home/ubuntu/islandora":{"guestpath":"/home/ubuntu/islandora","hostpath":"/home/daniel/Code/Environments/claw-playbook","disabled":false,"__vagrantfile":true}}} Looks like there's three spots where we have to specify the user directory. I can either update this PR to add a 'home directory' variable or can update the docs to list these as configs that need to be changed. |
README.md
Outdated
1. Install the roles using `ansible-galaxy`: `$ ansible-galaxy install -r requirements.yml` | ||
1. Provision the server with `$ ansible-playbook -i inventory/production -e "islandora_distro=ubuntu/xenial64"` | ||
1. Provision the server with `$ ansible-playbook -i inventory/production` | ||
- If the host you are provisioning is a Ubuntu 16.04 machine, you may wish to have the playbook install Python for you. This is a requirement to run the playbook. You can do this by passing an additional variable on the command line like this. `$ ansible-playbook -i inventory/production -e "islandora_distro=ubuntu/xenial64"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the command should be:$ ansible-playbook -i inventory/production playbook.yml -e "islandora_distro=ubuntu/xenial64"
I tested this PR against a Digital Ocean VM.
|
@dannylamb Could you rebase this please? @Natkeeran was able to test it and is ready to merge. |
@whikloj @Natkeeran rebased |
I must've clobbered the change with @Natkeeran's feedback. Think I did it straight in the browser and didn't pull that down to my local before rebase/force pushing. |
And apparantly @jonathangreen's pull as well... I have no idea what I did wrong there. Sry folks. Should be good now. |
@whikloj @jonathangreen |
This is how I ended up doing it. Any insight from other folks is appreciated.