Save time by using the taco-installer to get setup with a Taco Theme wrapped in the latest WordPress, add salts, and keep DB creds private, all automated. More features include: manual control of httpd passwords on a server, using a non-committed .env file for DB creds, and a robust .htaccess file.
Getting started is easy.
Download the taco-installer, cd into it’s root and run
composer install
Running this command automates the following tasks:
- installs the latest version of WordPress
- installs and sets up the Taco Theme
- (installs all necessary composer packages for Taco Theme to run correctly, most importantly, tacowordpress)
- applies salts to the
wp-config.php
file - loads database credentials from a
.env
file for easy setup and obfuscation- (ignored in .gitignore for better security)
After running composer install
, complete the following:
- update the
.env
file with your DB credentials and update table prefix variable, then configure your localhost and setup an empty database - Complete the welcome to WordPress steps once visiting your localhost, login to the CMS
- before you do anything, activate the Taco Theme under Appearance -> Themes.
For information about getting started with the Taco Theme's frontend task runners, view the theme’s README.md file.
For information on how to use tacowordpress, check out the repo. For complete documentation, see the wiki.
The taco-installer comes with a few other features:
- includes an
.htaccess
file with helpful variables for:- caching
- environment variables
- adding http password authentication configuration options
If you are running your site on an environment that requires password protection via the browser (htpasswd), you can set up authentication through a php script provided in the tools directory of this repo. Please follow these steps.
- ssh onto the server, and cd into the directory above "html". This will reflect the root folder of this repo.
- cd into "tools"
- type "
php htpass.php
" and follow follow the prompt
Note: This script will not work if there is already something in "html/.htaccess" pointing to a password file or a "htpasswd" file already exists.
@Jasand TBD...
WordPress core files are left out of version control to allow for WP to auto-update on production servers by default, as specified in the .gitignore
of this project. Auto-updating DB option is specified on the .env
file. Setup your version control to deploy the taco-installer files to a new server.
- deploy taco-installer to a new server
- ssh onto new server and run, just once,
composer install
in the root of the taco-installer
- This will perform all of the above actions on a new server,
- If you run composer install more than once in the root of the taco-installer, there are security checks as to not override files if they’ve already been installed.
- configure your
.env
file to point to the new server’s database - if the server requires password authentication through the browser (staging/dev environments), follow the configuration instructions for HTTP Password Config Options
- for composer updates in the theme, cd into the theme’s
/app/core
directory,
- run
composer update