The CopySite utility has been deprecated and replaced by the new DeploySite tool.
Deployment to a server is generally straightforward, as long as the minimum requirements are met and the basic steps are followed. If you're running into problems, check out the support options.
Deployment for Private Hosting, using a VPS or dedicated server is considerably easier. YetaWF includes the DeploySite tool to transfer your YetaWF sites to your server and to install the complete site on your server. Deploying a complete YetaWF site takes just a few minutes (depending on connection speed). While the site is updated, your site can optionally display a "Maintenance in Progress" page.
Shared Hosting is slightly more difficult because there are no server side tools that can be used, other than the tools provided by your hosting provider. These don't typically include YetaWF deployment.
In addition, deployment to Azure is also fully supported by YetaWF.
YetaWF makes extensive use of symlinks and cannot be deployed using Visual Studio Publish or dotnet publish. Instead, the DeploySite utility is used. The DeploySite utility can build a complete site in a local folder, ready for deployment using your favorite tool. Or it can be used to create a complete ZIP file with all data (optionally including SQL databases) and upload it via FTP to your server. On your server the DeploySite utility can also install the site.
The complete deployment process is defined by a yaml file, which is used to configure all options, including database backups and FTP uploads.
DeploySite Yaml File
Deploying to a Folder
Deploying to a ZIP file
Deploying to a Server (FTP)
Deploying to a Server (FTP, Blue/Green)
Deploying a Docker Container
YetaWF can be used with many Linux distros or in a Docker container.