# Install the external ~]$ sudo yum install -y yum-utils ~]$ sudo yum -y install # Change the EDB repo username and password ~]$ sudo sed -i "s/:/$YUMUSERNAME:$YUMPASSWORD/g" $REPOFILE # appropriate (these should not be run as ~]$ export ~]$ export ~]$ export ~]$ export ~]$ export REPOVERSION=edb # Export the variables used during the build, adjusting and as Let's get started! Steps (run as sudoer for security): # Install the EDB repo file locally as a ~]$ sudo yum install -y Note: The OS flavour on source and target machines should be the same otherwise some package level dependencies might not be resolved.Setup a local EDB YUM repository, or repo, on that disconnected network as a file based local repository (good for a small number of machines).Copy that clone to your disconnected machines (via one-way transfer, sneakernet, whatever options you have).Clone the EDB YUM repositories (the example below will do this with createrepo).It turns out that there is an easy and elegant way to address this, and it involves these steps: If you install any other way, we bundle OpenSSL and you'll need to get those patches from us which is not the most efficient way.īut, many of our customers (government, financial, and others) run their databases on machines that can not reach out to the internet, so they can't get patches from. RPMs leverage OS dependencies for things like OpenSSL meaning that you don't have to wait for EDB to patch Postgres in order to get an OpenSSL patch - if you install with RPMs.Some products are only available via RPMs.Updating is as simple as "yum update" rather than finding and downloading individual installers.It's easily integrated into Puppet, Chef, and other provisioning tools.It's the standard way to install on RHEL derivatives.
There are many, many reasons for this, a few of which are: If you are installing EDB on RHEL7 machines, RPMs are the way to go.
0 kommentar(er)
