By default, when you deploy an application to Azure App Service plan – your default web location will be under /home/site/wwwroot . /home/ is a persistent storage which means if you restart your application, your data will be still there. The problem with /home folder is that, it’s actually a network folder , which means every time you want to access files on this folder, it will do a network call. Some applications using some framework like Symfony , their library is huge, they read a lot of files , this will cause your application is very slow to respond. How do we fix this?Read More →

My advice is if you have a growing fast/busy table, you should keep it below 4GB, if it’s over 4GB, you should find away to archive it. This will need some helps from the code as well. Why shouldn’t you let it growing more than 4GB? It’s because sometimes your server crash, mysql might need to recover/repair the table. If the table is too big, it will take a lot of time to repair. While the table is repairing, you will be unable to access that table, this will put everyone in a long queue. Just imagine that you have a busy and it takesRead More →

When you run git status , you see the screen below No mater how you add these files (git add *) , the files are still not being committed or staged. Root cause: it’s because these folder has .git folder in side.Fix: remove .git folderRead More →

Azure stop supporting PHP7 in early 2023, for any reason you still wants to run PHP7, there is a way. Azure still allows us to run PHP7, this can be done via cli or using Azure Devops to deploy to php7.4 , Php 7.4 is the oldest version they allows. So, if you want to have PHP7 , PHP 7.4 is your only choice and you need to provision your resource via azure cli or devops pipelines. this can’t be done via Portal web interface. After you provision it, if you open in web interface, you might see it looks like this.Read More →

Azure App Service allows you to host your application on a managed environment. You select the environment/stack (Java, PHP,ASP.net…) , Azure will setup the environment for you by using container , all you need is to deploy your code to this environment. To deploy your code, Azure provides you some deployment tools: FTP/FTPS, Github, or local git. If you link your app with some tools like github,local git . This app service will automatically deploy your code when you commit your code (this can be turned off if you dont need) All these app service is based on containers. you can provide your own imageRead More →

Build vs Release : Build: you run it on a build server, this could be your default pool or agent pool (your self hosted pool) Release: it’s normally collect the data from Build , the tasks are similar , you can setup some workflows ( approval) , the biggest thing i can see is the deployment groups – We can run release on deployment groups, deployment groups is a group of servers that you target the deployment. When you start a build/release , the script will run on the build server/deployment groups. The script will pull the source code , then you can copy theRead More →

Will Symfony 2.3 Work with PHP 8? As the PHP ecosystem evolves, developers often find themselves facing the challenge of ensuring their applications and frameworks remain compatible with the latest versions of PHP. One common question that arises when upgrading to newer versions of PHP is whether older frameworks, like Symfony 2.3, will continue to work without issues. In this article, we will explore the compatibility of Symfony 2.3 with PHP 8, focusing on the potential challenges, solutions, and best practices for upgrading or maintaining legacy applications. What is Symfony 2.3? Symfony 2.3 is a long-term support (LTS) version of the Symfony framework, which wasRead More →