Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support hot reloading of configuration
See original GitHub issueAllow specifiying something like a --watch to make the runtime watch the provided configs and reload when they change.
Relevant comment from @jarupatj in #50:
You should look at using IOptionsMonitor https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options?view=aspnetcore-5.0#options-interfaces
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
Hot reloading configuration: why and how? - Clever Cloud
The ability to change the configuration of a running process is essential because launching new workers, transferring the current state between ...
Read more >Write and debug code by using Hot Reload - Visual Studio ...
You can configure Hot Reload by selecting Settings from the Hot Reload drop-down button. Or, open Tools > Options > Debugging > ....
Read more >NET Hot Reload support for ASP.NET Core
NET Hot Reload applies code changes, including changes to stylesheets, to a running app without restarting the app and without losing app state....
Read more >Understanding Hot Deployment and Hot Reloading in ...
Hot deployment and hot reloading can automatically update (reload or replace classes, etc.) the application while the application is running.
Read more >Hot Reload - Fluent Bit: Official Manual
Fluent Bit supports the hot reloading feature when enabled via the command line with -Y or --enable-hot-reload option.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Form the GraphQL side you need to implement an ITypeModule … this will manage the phase out of schemas…
Here you can see an example. https://github.com/ChilliCream/graphql-platform/blob/13349fa4af03514507ed5e3aaf9a771c696b56a6/src/HotChocolate/Fusion/src/Core/DependencyInjection/FileWatcherTypeModule.cs
The TypeModule is registered with the schema.
Hot reload is supported only when:
When “{current runtime} mode” == “development” then Supported. Otherwise, they must restart the service. “This is a developer feature”