|
| 1 | +Blogifier is server-side ASP.NET Core application that can be deployed to different environments and even operating systems. |
| 2 | +Below several common scenarios to run and troubleshoot locally before application deployed to host server. |
| 3 | + |
| 4 | +### Run in Visual Studio |
| 5 | +1. Open solution in Visual Studio, right-click `App` project in solution explorer and set it as startup project |
| 6 | +2. Run in debug mode and make sure application runs in the web browser |
| 7 | +3. In the browser, open developer tools, refresh page and make sure no errors show up in the console |
| 8 | + |
| 9 | +If all looks good, application is ready for deployment |
| 10 | + |
| 11 | +### Deploy and Run from Local Folder |
| 12 | +Use steps outlined in the [build section](https://github.com/blogifierdotnet/Blogifier/blob/master/docs/Build.md) |
| 13 | +to publish application to the local folder and run it using `dotnet App.dll` command. |
| 14 | +Again, open developer tools and verify no client-side errors thrown in the JavaScript console. |
| 15 | + |
| 16 | +### Deploy to Host Server |
| 17 | +The output produced and verified in the local deployment step is exactly what needs to be published to the host. |
| 18 | +Usually your host provides information how to upload and set up application on remote server. |
| 19 | +It can differ, but important things are: |
| 20 | + |
| 21 | +1. Verify application runs locally (steps above) |
| 22 | +2. Move all files from the `build/publish` folder to your remote host |
| 23 | +3. Run application on your remote hosting server |
| 24 | +4. Verify with development tools there no errors (same as in previous steps) |
| 25 | + |
| 26 | +If at any point during this process you run into errors, |
| 27 | +please post them to [Github issues](https://github.com/blogifierdotnet/Blogifier/issues) along with **steps to re-produce the error**. |
| 28 | +Without steps to re-produce the error, it is hard or even not possible to fix it. |
| 29 | + |
| 30 | +> It is common that application runs fine locally and only has issues when deployed, because remote host does not properly setup or configured. |
| 31 | +It is also common that application was modified/changed to meet custom conditions. |
| 32 | +If so, it is important to identify what is the difference between standard and modified version. |
0 commit comments