Background I’ve been working on introducing a Content Security Policy (CSP) for some time and today is the day where a first, minimal version of our policy will start to be enforced. So, what’s a Content Security Policy? Mozilla explains it like this: Content Security Policy (CSP) is a feature that helps to prevent or minimize the risk of certain types of security threats. It consists of a series of instructions from a website to a browser, which instruct the browser to place restrictions on the things that the code comprising the site is allowed to do.

Rapid Release and Continuous Delivery Rapid release in the name of a project to make releases more frequent and deploy bugfixes more rapidly. This is a project which will require company-wide changes over many years but here I’ll focus on some upcoming changes to continuous delivery (CD) which will get us just a bit closer to making releases “rapid”. The Changes Operations is in the process of changing how CD works with the goal to make it possible to deploy production systems automatically.

tco - Copy Only What’s Needed tco has recently been updated to allow skipping tables rarely used during development. Another change will be rolled out shortly which will make skipping various tables the default when copying to localhost. This will help safe space and time. In an initial release, the following tables will be skipped: nice_email_archive nice_email_archive_to_address nice_email_archive_to_email_attachment nice_email_archive_to_recipient nice_entity_history nice_log_entry nice_log_entry_var nice_notification nice_progress_var nice_system_activity nice_task_execution nice_task_progress tco will clearly indicate when tables are skipped: