Let's list preferences that should not be the same. This is useful if you copy a site from development to production. They could be part of environment variables. You can set via System Configuration.
- db/local.php (unless on different servers)
- unified_elastic_index_prefix (if both point to the same Elasticsearch instance or cluster)
- Authentication method: If you are connection to Active Directory or LDAP in production, you may want to change this setting in development
- cookie_name (unless on different domain)
- domain redirect
- New in Tiki22: Catch all email so you can test everything without spamming users
- .htaccess setting; You may not have full control over the servers (Apache modules, etc).
Also: If Tiki is not in the root web directory, you usually have to set the Apache RewriteBase in htaccess. This could different between your environments.
- Security & Performance setting; The production domain and website may use different security setting than the development website (SSL certificate). Same goes for performance setting that are usually OFF while developing and should be enable and tuned on prod.
See also here: https://tiki.org/Pre-Dogfood+Server#System_Configuration
Also to be careful about: If you are storing files on disk and dev / staging / prod are on the same server (ex: with sub-domains): You should make sure they are pointing to different directories (otherwise, you delete a file on the dev server, and it deletes it on the production server, because the storage is shared). See ideal scenario for file storage
|Pref name||Path of storage for feature (if stored in directory)|
|w_use_dir||Wiki page attachments|
|In each forum||Forums|
- New in Tiki19: https://sourceforge.net/p/tikiwiki/code/67442
- Configuration Management for Tiki Projects
- TRIM Revamp
- Continuous upstream