Skip to content
This repository has been archived by the owner on Oct 3, 2019. It is now read-only.

Use yum proxy settings to install behind squid3 #88

Open
wants to merge 28 commits into
base: petiepooo
Choose a base branch
from
Open

Use yum proxy settings to install behind squid3 #88

wants to merge 28 commits into from

Conversation

petiepooo
Copy link

This sequence of updates allows me to install everything behind a squid3 proxy. The deploy script reads the proxy setting from the yum.conf file and adds appropriate flags or variables to all calls that retrieve things from the internet.

NOTE: I have not verified this works without a proxy, but I believe it should. My intention was that all commands should work as originally intended when the proxy variables I set from parsing yum.conf are empty or nonexistent. Please test without a proxy before considering a merge to master.

I also added a purge script so I can test things without needing to restore a VM snapshot ore redeploying the OS. It's not perfect, in that it leaves several things around, like dependent packages and users created by the deploy script.

The install script no longer installs components if it sees the resulting service is active. This was added in response to issue #87. To reinstall a component, just stop the service (and delete any files that block reinstallation; check the purge script for details). The beat services are reinstalled in any case, and es, thehive, and cortex are all reinstalled if es is not active.

Copy link
Collaborator

@peasead peasead left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason you opted for erase vs. remove?

@petiepooo
Copy link
Author

Habit? Coming from debian-based distro, there's a difference between remove and purge, and I want to delete configuration files too so its as close to a fresh install as I can get. I see now that erase and remove are aliases in yum, and I'm explicitly removing the config directories anyway. I'll update to your prefered verb.

@peasead peasead changed the base branch from master to petiepooo November 12, 2018 16:39
purge_capes.sh Outdated Show resolved Hide resolved
deploy_capes.sh Show resolved Hide resolved
deploy_capes.sh Show resolved Hide resolved
deploy_capes.sh Show resolved Hide resolved
deploy_capes.sh Show resolved Hide resolved
deploy_capes.sh Show resolved Hide resolved
deploy_capes.sh Show resolved Hide resolved
landing_page/index.html Show resolved Hide resolved
deploy_capes.sh Show resolved Hide resolved
deploy_capes.sh Show resolved Hide resolved
@peasead
Copy link
Collaborator

peasead commented Nov 12, 2018

@petiepooo I'm sorry for the spam. These are just a lot of commits for a lot of issues in one PR; so I'm trying to sort through them.

@peasead peasead self-assigned this Nov 12, 2018
@petiepooo
Copy link
Author

@peasead no problem. I didn't realize as I was adding comments to the PR that each one would require a separate approval.. sorry.

@petiepooo
Copy link
Author

Do I need to do anything regarding the review? I'm not used to these github features yet...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants