4 ms·

So many things. One that is irritating me a lot right now is how complex it is to deploy to an "App Service" and how nothing seems to work. Also it's incredibl

So many things. One that is irritating me a lot right now is how complex it is to deploy to an "App Service" and how nothing seems to work. Also it's incredibly slow. https://github.com/Azure/webapps-deploy/issues/60 https://github.com/Azure/webapps-deploy/issues/60 And the fact that we're locked into using it means I have to take my 50 second netlify deploy and migrate it to a 15 minute ADO deploy, losing out on loads of features and gaining none.

jiggawatts 4y ago
Just put your web app in a container and call it a day? App Service can run containerised workloads just fine.
- AndrewVos 4y ago
  I would love to get this done quick. Do you have a link to something usable?
  - jiggawatts 4y ago
    This depends almost entirely on what exactly you are hosting. Is it a Node.js app? ASP.NET? Windows? Linux? In Visual Studio it is more-or-less as simple as right-clicking a project and selecting "Add -> Docker support": https://learn.microsoft.com/en-us/dotnet/architecture/containerized-lifecycle/design-develop-containerized-apps/visual-studio-tools-for-docker https://learn.microsoft.com/en-us/dotnet/architecture/contai... In Azure DevOps pipelines or GitHub Actions, it's also quite simple to add a container build step: https://learn.microsoft.com/en-us/azure/devops/pipelines/ecosystems/containers/build-image https://learn.microsoft.com/en-us/azure/devops/pipelines/eco... In the actual Azure subscription you just need to create an Azure Container Registry resource to host the image. I believe you can also use Docker Hub, if you prefer. Then in App Service just host the container image instead of the raw code: https://learn.microsoft.com/en-us/azure/app-service/tutorial-custom-container https://learn.microsoft.com/en-us/azure/app-service/tutorial... That should be about it. The effect of this is to "zip up" your loose 'js' files (or whatever), making deployments much faster. The build happens before this step, so the container image is "final" and will run directly without needing any npm steps or whatever at deployment time. If you need something like hot-reload or similar very fast deployment times, then App Service is probably not the right environment for you. However, with containers its often possible to have a fast local deployment edit-build-test loop and then have the same environment running in production. This is the main benefit of containers!
    - AndrewVos 4y ago
      Sorry but I don't want to install Microsoft's text editor to deploy an app. It's a basic next.js app, nothing special. I tried the app service config on GitHub actions and it was ridiculous to say the least. 15 minutes to copy the files over and then it didn't launch the app correctly even after I specified how to launch it. Pitfalls at every step. It's like the UI was designed by a child. You're saying a lot of "just", and to be honest those tasks aren't simple things that I can just do. For example having a docker registry that I now have to secure and babysit is not what I'm here for. I'm not sure why you're trying to argue that Azure is good.
    - AndrewVos 4y ago
      Also I don't want to have the Devs in my team have to use containers where had no need for them before. It's not a nice cross platform experience. Sorry if I'm sounding defensive here, but I'm really not into having a worse experience just to fit I to Microsoft's hellscape.

jiggawatts 4y ago

Just put your web app in a container and call it a day? App Service can run containerised workloads just fine.

AndrewVos 4y ago
I would love to get this done quick. Do you have a link to something usable?
- jiggawatts 4y ago
  This depends almost entirely on what exactly you are hosting. Is it a Node.js app? ASP.NET? Windows? Linux? In Visual Studio it is more-or-less as simple as right-clicking a project and selecting "Add -> Docker support": https://learn.microsoft.com/en-us/dotnet/architecture/containerized-lifecycle/design-develop-containerized-apps/visual-studio-tools-for-docker https://learn.microsoft.com/en-us/dotnet/architecture/contai... In Azure DevOps pipelines or GitHub Actions, it's also quite simple to add a container build step: https://learn.microsoft.com/en-us/azure/devops/pipelines/ecosystems/containers/build-image https://learn.microsoft.com/en-us/azure/devops/pipelines/eco... In the actual Azure subscription you just need to create an Azure Container Registry resource to host the image. I believe you can also use Docker Hub, if you prefer. Then in App Service just host the container image instead of the raw code: https://learn.microsoft.com/en-us/azure/app-service/tutorial-custom-container https://learn.microsoft.com/en-us/azure/app-service/tutorial... That should be about it. The effect of this is to "zip up" your loose 'js' files (or whatever), making deployments much faster. The build happens before this step, so the container image is "final" and will run directly without needing any npm steps or whatever at deployment time. If you need something like hot-reload or similar very fast deployment times, then App Service is probably not the right environment for you. However, with containers its often possible to have a fast local deployment edit-build-test loop and then have the same environment running in production. This is the main benefit of containers!
  - AndrewVos 4y ago
    Sorry but I don't want to install Microsoft's text editor to deploy an app. It's a basic next.js app, nothing special. I tried the app service config on GitHub actions and it was ridiculous to say the least. 15 minutes to copy the files over and then it didn't launch the app correctly even after I specified how to launch it. Pitfalls at every step. It's like the UI was designed by a child. You're saying a lot of "just", and to be honest those tasks aren't simple things that I can just do. For example having a docker registry that I now have to secure and babysit is not what I'm here for. I'm not sure why you're trying to argue that Azure is good.
  - AndrewVos 4y ago
    Also I don't want to have the Devs in my team have to use containers where had no need for them before. It's not a nice cross platform experience. Sorry if I'm sounding defensive here, but I'm really not into having a worse experience just to fit I to Microsoft's hellscape.