Skip to content

Commit 08bfd5f

Browse files
committed
Added troubleshooting doc
1 parent c7a1978 commit 08bfd5f

File tree

3 files changed

+36
-3
lines changed

3 files changed

+36
-3
lines changed

Blogifier.sln

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Microsoft Visual Studio Solution File, Format Version 12.00
3-
# Visual Studio 15
4-
VisualStudioVersion = 15.0.27428.2011
3+
# Visual Studio Version 16
4+
VisualStudioVersion = 16.0.28803.352
55
MinimumVisualStudioVersion = 10.0.40219.1
66
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Solution Items", "Solution Items", "{4E0164ED-2249-4973-B3FD-180172EBCD0A}"
77
ProjectSection(SolutionItems) = preProject
@@ -36,6 +36,7 @@ Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "docs", "docs", "{6015AFDB-9
3636
docs\SendGrid.md = docs\SendGrid.md
3737
docs\SqlServer.md = docs\SqlServer.md
3838
docs\Themes.md = docs\Themes.md
39+
docs\Troubleshooting.md = docs\Troubleshooting.md
3940
docs\VideoAudio.md = docs\VideoAudio.md
4041
EndProjectSection
4142
EndProject

docs/Troubleshooting.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
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.

src/App/Pages/_Index.cshtml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@
3131
<header class="header">
3232
<div class="container">
3333
<nav class="navbar navbar-expand-lg navbar-dark p-0">
34-
<a class="navbar-brand" href="~/blog"><img src="~/assets/img/logo.png" alt="Blogifier"></a>
34+
<a class="navbar-brand" href="~/blog"><img src="~/home/img/logo.png" alt="Blogifier"></a>
3535
<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation"><span class="navbar-toggler-icon"></span></button>
3636
<div class="collapse navbar-collapse" id="navbarSupportedContent">
3737
<ul class="navbar-nav">

0 commit comments

Comments
 (0)