Blog posts by Szołkowski Blog2025-10-08T10:30:37.0000000Zhttps://world.optimizely.com/blogs/szokowski-blog/Optimizely WorldQuiet Performance Wins: Scheduled Job for SQL Index Maintenance in Optimizelyhttps://szolkowski.github.io/2025/10/08/Quiet-Performance-Wins-Scheduled-Job-for-SQL-Index-Maintenance-in-Optimizely2025-10-08T08:00:00.0000000Z2025-10-08T10:30:37.0000000Zstanislaw.szolkowski@firstlinesoftware.comAs Optimizely CMS projects grow, it’s not uncommon to introduce custom tables—whether for integrations, caching, or specialized business logic. But with great schema comes great responsibility: SQL Server indexes and statistics need love too.How to automatically remove orphaned Opti jobs from the DBhttps://szolkowski.github.io/2025/09/04/automatically-removing-orphaned-jobs-from-db2025-09-04T08:00:00.0000000Z2025-09-04T10:30:43.0000000Zstanislaw.szolkowski@firstlinesoftware.comOptimizely CMS provides a simple yet powerful built-in job system that handles most standard scheduling scenarios with ease. Developers can easily implement these jobs to run automatically on a defined schedule or trigger them manually through the CMS interface. From my experience as an Optimizely/Episerver developer, manual jobs are especially useful for one-off operations or bulk content updates. Typically, these jobs serve a temporary purpose and are removed from the codebase in subsequent releases once they’ve fulfilled their role.Tunning Application Insights telemetry filtering in Optimizelyhttps://szolkowski.github.io/2025/06/12/episerver-and_application_insights_filters2025-06-12T08:00:00.0000000Z2025-06-12T10:31:10.0000000Zstanislaw.szolkowski@firstlinesoftware.comApplication Insights is a cloud-based service designed to monitor web applications, providing insights into performance, errors, and user behavior, which integrates very well with the Optimizely CMS/Commerce solution and is included in the default DXP experience. However, like any generic tool for complex systems, it can be tuned to work even better for specific platforms and projects.Running full Optimizely development setup on M1 (ARM) based machinehttps://szolkowski.github.io/2025/05/26/episerver-on-apple-silicon-20252025-05-26T08:00:00.0000000Z2025-05-26T10:31:16.0000000Zstanislaw.szolkowski@firstlinesoftware.comA few years ago I posted post about how to run Optimizely/Episerver on M1 (ARM) based machine, so I think it is high time to revisit and check what did change.Adding Hangfire to Episerver/Optimizely CMS 12https://szolkowski.github.io/2024/07/31/adding-hangfire-to-epi-122024-07-31T12:57:48.0000000Z2024-07-31T13:31:01.0000000Zstanislaw.szolkowski@firstlinesoftware.comEpiserver/Optimizely contains build ScheduledJobs support which does its job for internal EPI jobs and simple custom cases, however, when the app grows and we need more and more jobs it fails behind dedicated solutions.Adding Hangfire to Episerver/Optimizely CMS 12https://szolkowski.github.io/2024/07/11/adding-hangfire-to-epi-122024-07-11T10:46:48.0000000Z2024-07-31T13:00:55.0000000Zstanislaw.szolkowski@firstlinesoftware.comEpiserver/Optimizely contains build ScheduledJobs support which does its job for internal EPI jobs and simple custom cases, however, when the app grows and we need more and more jobs it fails behind dedicated solutions.Add SonarCloud/SonarQube to Episerver/Optimizely 12 project using Github actionshttps://szolkowski.github.io/2023/08/15/add-sonarcloud-to-epi-12-pipeline2023-08-15T17:31:48.0000000Z2024-07-31T13:00:56.0000000Zstanislaw.szolkowski@firstlinesoftware.comIn my previous post Add Github pipelines/workflows to Episerver 12 project I have briefly explained how to add simple pipeline/workflow to Episerver/Optimizely 12 project. Having project build for each PR and on main branch push is nice improvement, but we can make it even better. For this example I will add SonarCloud integration to my existing workflow from my previous post. You can see it on my Foundation fork - it will be using Github actions on each pull request and on main branch.Add Github pipelines/workflows to Episerver 12 projecthttps://szolkowski.github.io/2022/07/30/add-github-pipeline-to-epi-122022-07-30T15:31:48.0000000Z2024-07-31T13:00:56.0000000Zstanislaw.szolkowski@firstlinesoftware.comWith Episerver 12 moving to .NET 5/6 civilization come to devops handling of Episerver projects and we can easily integrate modern CI approaches using pipelines. For this example I will add simple building of my Foundation fork using Github version of pipelines called “workflows” on each pull request and on main branch.Episerver Foundation on Apple Silicon (M1)!https://szolkowski.github.io/2022/07/28/episerver-on-apple-silicon2022-07-28T19:29:19.0000000Z2024-07-31T13:00:57.0000000Zstanislaw.szolkowski@firstlinesoftware.comWith introduction of .NET 6 Episerver/Optimizely packages developing it on M1 machine is now possible, however there are still some problems with initial configuration, but lets not go ahead of ourself.