Can`t even start in dev mode

[say1j]

Drops when going to localhost:5000 on dev mode with dotnet watch run

fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1]
      An unhandled exception has occurred while executing the request.
System.InvalidOperationException: No file provider has been configured to process the supplied file.
   at Microsoft.AspNetCore.Mvc.Infrastructure.VirtualFileResultExecutor.GetFileInformation(VirtualFileResult result)
   at Microsoft.AspNetCore.Mvc.Infrastructure.VirtualFileResultExecutor.ExecuteAsync(ActionContext context, VirtualFileResult result)
   at Microsoft.AspNetCore.Mvc.VirtualFileResult.ExecuteResultAsync(ActionContext context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultAsync(IActionResult result)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext[TFilter,TFilterAsync](State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultFilters()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|19_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
   at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
   at Swashbuckle.AspNetCore.ReDoc.ReDocMiddleware.Invoke(HttpContext httpContext)
   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

What i need to do in dev?
Api key was pasted (DDdb+rovzYczvCqCXgFJBllHddj8FHR9aLTSdQ98kXA=), but any way

[trinitrotoluene]

Hi, can you confirm for me that you've got the client submodule pulled locally? That exception occurs when the middleware that serves the SPA can't find the index.html file that it serves to load it.

[say1j]

$ dotnet watch run (from here)

result browser

result visual

Hi, can you confirm for me that you've got the client submodule pulled locally? That exception occurs when the middleware that serves the SPA can't find the index.html file that it serves to load it.

[trinitrotoluene]

The error is coming from the backend expecting a wwwroot folder to be present to serve files from, and this folder is created by the client app during deployment.

To pull in the missing client-app submodule

$ git submodule update --init --recursive

then install and run the client app in src/StatusWatchdog/client-app

$ npm install
$ npm run watch

once it's running you can start dotnet watch run in a new terminal (you can do this from vscode) and both projects will live-reload as you edit them.

That said, if you just want to test/get an idea of the state the project is currently in, you might want to just run it using the docker-compose configuration in the README. It'll save you the extra work of configuring a PostgreSQL database for the backend to talk to.

[say1j]

The error is coming from the backend expecting a wwwroot folder to be present to serve files from, and this folder is created by the client app during deployment.

To pull in the missing client-app submodule

$ git submodule update --init --recursive

then install and run the client app in src/StatusWatchdog/client-app

$ npm install
$ npm run watch

once it's running you can start dotnet watch run in a new terminal (you can do this from vscode) and both projects will live-reload as you edit them.

That said, if you just want to test/get an idea of the state the project is currently in, you might want to just run it using the docker-compose configuration in the README. It'll save you the extra work of configuring a PostgreSQL database for the backend to talk to.

okay, i`ll try it