{ Archive }

{ redirect }

Backdrop Logo

So excited to announce my first drupal to backdrop module port redirect. You can find it, download it, and install it on your backdrop install here: https://github.com/backdrop-contrib/redirect

Of course special thanks to the drupal authors and maintainers of the drupal redirect module.

Working on this port was great fun and a great learning experience! If you want to work on a port you can find some guidelines and a nice video over at https://api.backdropcms.org/converting-modules-from-drupal. You can also get great general info at Backdrop CMS API

And of course one of my favourite parts of working on backdrop is the #dev team; special thanks to @quicksketch and @jenlampton for mentoring. Come join us on irc #backdrop channel on freenode.

{ 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.

# Ignore paths that contain user-generated content.

# Ignore sass stuff.

# Ignore PHPStorm stuff.

tweets away;

{ 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';