You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tsak's HotReloadService scans Libs/ every 10s — once the .tpkg lands there, it hot-swaps the route graph. The module appears in the dashboard without restart.
The question is whether this deserves a first-class nuget:// transport or a dedicated built-in Tsak module with a simple config:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
NuGet feed watcher as a built-in module
@jakenuts raised this on Reddit — wanted to keep the idea alive on GitHub.
The concept: a module that polls a NuGet feed, detects a new version of your package, downloads it and hot-swaps the .tpkg without restart.
You can wire this today manually:
Tsak's HotReloadService scans
Libs/every 10s — once the .tpkg lands there, it hot-swaps the route graph. The module appears in the dashboard without restart.The question is whether this deserves a first-class
nuget://transport or a dedicated built-in Tsak module with a simple config:{ "nuget-watcher": { "package": "MyApp.Module", "feed": "https://api.nuget.org/v3/index.json", "interval": "60s", "drop-path": "Libs/" } }Happy to help prototype it. The module entry point is
InitRoute.main(IRouteContext)— that's the entire contract.What would you use this for?
Beta Was this translation helpful? Give feedback.
All reactions