Logical choice was therefore FTP/FTPS Server. Obviously, for publishing directly to Linux host in order to be served with same web server ( Apache or Nginx ) as WordPress site, I had to ignore Azure and IIS, and even Docker options. While manual publishing of files to any host is always possible, what I needed is “one-click” publish integrated in standard Visual Studio publish process ( right-click VS project, ‘publish’ ), and currently supported options are: How to publish dotnet core app from Visual Studio to your Linux host in the most efficient way ?
to have sites under my domain, at reasonable priceĪzure allows using your domain instead of, but if you want also SSL on those custom domains ( which you must have in order to install PWA apps, like ), then Azure require moving to at least B1 tier – which is both more expensive ( over $50/month, compared to $0 for F1 or under $10/month for D1 ) and with worse performance ( just 1 CPU, compared to multiple CPUs on shared F1/D1 plans ).īut while reasons for publishing dotnet apps on Linux hosts instead of Azure will be different and subjective for most people, problem remains same :.to reuse same DigitalOcean droplet used for this WordPress site.But I decided to use Linux as publish target due to two reasons:
Initially I published my Blazor proof-of-concept projects to Azure, and that is fairly straightforward to setup in Visual Studio ( after initial fairly complicated Azure site setup ).
0 kommentar(er)
