XF 1.2 How portable is the XF setup?

I am trying to set up my deployment workflow for XF. Right now this is how I make changes:

1. Pull from private repository. Pull production database from live and apply to local devel database.
2. Make changes on devel branch and merge to master when fully tested / approved.
3. Push changes. Deploy hook moves changes into production and automates restarting php5-fpm and nginx.

This workflow breaks if XF stores any config changes in the database. I'll assume add-ons won't work with this set up. I'm not talking about user/node permission changes; but are appearance settings or anything in options DB backed?

What's a proper dev->production workflow for XF?

Liam W

Well-known member
Everything in options is stored in the database.

Even templates are stored in the database.

Manually test on dev, manually push to production. Best way.


Liam W

Well-known member
It does allow for easy transfer of a complete install though - just copy the database and it's set up (as long as addon files are present etc.).