Title: livereload not (reliably) working with devcontainers that share the same uniform port configuration when forwarding ports to host · Issue #253 · docsifyjs/docsify-cli · GitHub
Open Graph Title: livereload not (reliably) working with devcontainers that share the same uniform port configuration when forwarding ports to host · Issue #253 · docsifyjs/docsify-cli
X Title: livereload not (reliably) working with devcontainers that share the same uniform port configuration when forwarding ports to host · Issue #253 · docsifyjs/docsify-cli
Description: As a developer who uses devcontainers a lot I have to reuse the same devcontainer features sets as much as possible in order to avoid long devcontainer build times as well as storage explosion -- by sharing a uniform configuration of a s...
Open Graph Description: As a developer who uses devcontainers a lot I have to reuse the same devcontainer features sets as much as possible in order to avoid long devcontainer build times as well as storage explosion -- b...
X Description: As a developer who uses devcontainers a lot I have to reuse the same devcontainer features sets as much as possible in order to avoid long devcontainer build times as well as storage explosion -- b...
Opengraph URL: https://github.com/docsifyjs/docsify-cli/issues/253
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"livereload not (reliably) working with devcontainers that share the same uniform port configuration when forwarding ports to host","articleBody":"As a developer who uses devcontainers a lot I have to reuse the same devcontainer features sets as much as possible in order to avoid long devcontainer build times as well as storage explosion -- by sharing a uniform configuration of a single docsify server port instead of two (the second for livereload/hot reloading).\n\nThe problem is \"a choice between the devil and the deep blue sea\":\n- either have a uniform docsify port configuration (such as 3300) across all my devcontainer configuration, as mandated by company policy, and have livereloading broken because the devcontainer's livereload port is never the same port number as the forwarded livereload port;\n- or configure each and every devcontainer differently in order to use unique ports, which is not only cumbersome and error-prone, but blocked many times by company policies.\n\nPlease integrate the livereload port into a single contents+livereload notifications port. Other tools allow this for a long time. Thank you!","author":{"url":"https://github.com/thediveo","@type":"Person","name":"thediveo"},"datePublished":"2026-06-25T18:08:49Z","url":"https://github.com/docsifyjs/docsify-cli/issues/253"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:950cb661-ed47-2acd-a704-791165b0ba0e |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | C8C0:14C89B:24A76C8:33137B5:6AFD3A60 |
| html-safe-nonce | 7da564dafe972209694f8d7247c41d86735704d5d0b080bb7bc17659a4381871 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDOEMwOjE0Qzg5QjoyNEE3NkM4OjMzMTM3QjU6NkFGRDNBNjAiLCJ2aXNpdG9yX2lkIjoiNzEyMDc1NjkzMDQ0MzU1NzQ3MiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | b361263fd911b4076ec44a74ae932c9be6113b1ebf886454f333a4a380e7e581 |
| hovercard-subject-tag | issue:4746292259 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/docsifyjs/docsify-cli/253/issue_layout |
| twitter:image | https://opengraph.githubassets.com/712cd0910ef4c2ca068b7ceaebabdf3d4b8819cf567fa95c5fe9ad6ac2523671/docsifyjs/docsify-cli/issues/253 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/712cd0910ef4c2ca068b7ceaebabdf3d4b8819cf567fa95c5fe9ad6ac2523671/docsifyjs/docsify-cli/issues/253 |
| og:image:alt | As a developer who uses devcontainers a lot I have to reuse the same devcontainer features sets as much as possible in order to avoid long devcontainer build times as well as storage explosion -- b... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | thediveo |
| hostname | github.com |
| expected-hostname | github.com |
| None | bdbacc25b921224ff0befcb9e629560a1255be51aec9991d6e3f95b5e9151474 |
| turbo-cache-control | no-preview |
| go-import | github.com/docsifyjs/docsify-cli git https://github.com/docsifyjs/docsify-cli.git |
| octolytics-dimension-user_id | 40133106 |
| octolytics-dimension-user_login | docsifyjs |
| octolytics-dimension-repository_id | 74482617 |
| octolytics-dimension-repository_nwo | docsifyjs/docsify-cli |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 74482617 |
| octolytics-dimension-repository_network_root_nwo | docsifyjs/docsify-cli |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 556dd37bb0aceffb25724e151b5d858b3265b40b |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width