Community Auth currently provides some shell scripts that help you get up and running quickly. None of these scripts are required for the install process, and they’ll only work for Linux and Mac users. There are some assumptions made in regards to running these scripts, and you know what they say about assumptions.
- They will be made executable using chmod.
- The script will be in the proper location before you execute it.
- Bash is located at /bin/bash.
A Description of the Scripts
.install.sh – a script that copies Community Auth files to your application.
.optional_fast_install.sh – downloads CodeIgniter and Community Auth, extracts them, and copies Community Auth files to the newly created application.
.development_install.sh – clones the Community Auth repository, downloads and extracts CodeIgniter, creates a database for you, and configures everything. All you need to do is create a user, and you’re ready to join the Community Auth development team. Get it HERE.
If you are starting from scratch and want the quickest install possible, simply cd into your project root, place .optional_fast_install.sh there and run it. After that, you will only need to do steps 8 through 17 of the installation procedure. This is really the best option if you just want to check out Community Auth to see if it’s right for you.
If you already have an existing project and want to integrate Community Auth into it, .install.sh is your best option. Running this script copies the necessary files into your application. If you choose this option, you can skip steps 4 through 7 of the installation procedure, and go straight to step 8.
The .development_install.sh script is not likely something that most people will want to use. I created this script for easier development environment setup of Community Auth. If you choose this installer, you’ll place the script in the same directory as where you want git to clone the Community Auth repository.
Making the scripts executable
Permission to execute a file is not normally granted automatically, so you’ll need to make each file executable.
# Example command to make install.sh executable sudo chmod 755 ./install.sh
Where is Your Bash?
Since the shebang line of each of the installer scripts reads #!/bin/bash, if your bash isn’t located there, your terminal will tell you that it unable to execute it. If that’s the case, then you’d need to update the shebang line with the location of your bash, which can be found running the following command:
Run the Script(s)
Now, if the shebangs match the location of your bash, and the file(s) you want to execute are executable, you’ll simply run them.
# Run install.sh from the application directory sudo ./third_party/community_auth/sh/install.sh