Basic initial CentOS 7 setup script.

Installs common/base CentOS 7 repositories/programs (x86_64)

c7repos.sh attempts to installs/create the following repositories configurations

and some suggested extra packages for a clean, practical and usable base server system. c7repos.sh also defines a bunch of useful system aliases and functions.

Some repositories have options that can be enabled directly in the repo files themselves (located in /etc/yum.repos.d/). REMI, per example, contains all PHP versions easily enableable from the repository files. Per example, EL-REPO's latest kernel packages kernel-ml, is also just a digit away from being enabled. YUM can also be run with the extra switch --enablerepo=repo.name, essentially doing the same. Alot more YUM stuff to be read in the manual or by visiting YUM's Official webpage

c7repos.sh code repository is hosted on GitHub.

The installable script is accessible via the traditionnal GitHub's raw url and is also 'mirrored' using both short following url providers Git.io and Bit.ly. Its also available via 4ce.ca but this method cannot be used in conjunction with curl/bash (Method #2, redirect problem).

Preferably from a FRESHLY INSTALLED CentOS 7 server, c7repos.sh can be called as superuser (root) using one of the following methods

• Executing, as root, from a known mirror.

Examples:

root@host ~ # bash <(curl -4sLk https://bit.ly/c7repos)
root@host ~ # bash <(curl -4sLk https://git.io/c7repos-install)
root@host ~ # bash <(curl -4sLk https://git.io/vd7Ye)

• Piping curl's output to bash's input.

Examples:

root@host ~ # curl -4sLk https://bit.ly/c7repos | bash -
root@host ~ # curl -4sLk https://git.io/c7repos-install | bash -
user@host ~ $ curl -4sLk https://git.io/vd7Ye | sudo bash -

• Downloading/saving it to a location on the machine and executing with bash.

Examples:

root@host ~ # wget https://bit.ly/c7repos -O /tmp/c7repos.sh
root@host ~ # bash /tmp/c7repos.sh

You MUST be superuser (root) in order to run c7repos.sh (sudo works as well). Using Bit.ly mirror is just about the same as using GitHub's raw repository url directly the only difference being that i can potentially monitor the usage at some point and if need be. If you do not want to go thru Bit.ly you are free to run directly from either one of GitHub's addresses, Git.io's short 1, Git.io's short 2 or GitHub's raw url.

Bit.ly mirror GitHub's raw url Git.io's short url 1 Git.io's short url 2 4ce.ca gh-pages

Originally coded for CentOS 6 by Peggy following a request for a simple server configuration script. From there on and some time later, it grew to something a little more actual and practical. (Peggy is a fictitious character)

A changelog is available (and hopefuly up-to-date) on GitHub

By all means and please, do not hesitate to send comments, ideas and/or pull requests.