{ Archive }

{ A useful .gitignore }

Backdrop Logo
I usually ignore the css files and just version the sass files and compile sass on deploys.
Here is a useful .gitignore file for backdrop:


# Ignore configuration files that may contain sensitive information.
settings.php
sites/*/settings*.php

# Ignore paths that contain user-generated content.
files
private
sites/*/files
sites/*/private

# Ignore sass stuff.
.sass-cache
stylesheets

# Ignore PHPStorm stuff.
.idea
*.idea/*

tweets away;
@serundeputy

{ Backdrop from Local to Live Server }

Backdrop Logo

You install backdrop, you configure it, theme it, make some modules; how to get it to the server?

With the new Configuration Management Initiative (CMI) things are a little different.

My usual steps are to pull in the code base with git:


git pull origin {your_awesome_branch_name}

Push up your files:

rsync -av files/ user@{server_url:/path/to/backdrop/root/files}

Push up your database:


mysql -u {your_db_user} -p {awesome_db_name} < {your_sql_dumpfile.sql} -h {database_server_ip_address}

Then visit my URL. In this case though it did not work.

Enter settings.php in which you will now find variables that you can point to your chosen config settings directories:


$config_directories['active'] = 'files/config_<hash>/active';
$config_directories['staging'] = 'files/config_<hash>/staging';

Pages