Title: Container specific configuration · Issue #4 · VirtualProgrammingLab/documentation · GitHub
Open Graph Title: Container specific configuration · Issue #4 · VirtualProgrammingLab/documentation
X Title: Container specific configuration · Issue #4 · VirtualProgrammingLab/documentation
Description: Why is the generic "resources" namespace used for (docker) container specific configurations? resources.volume, resources.image I think we should also go through all configuration names, currently they are all namespaced with the old pha...
Open Graph Description: Why is the generic "resources" namespace used for (docker) container specific configurations? resources.volume, resources.image I think we should also go through all configuration names, currently ...
X Description: Why is the generic "resources" namespace used for (docker) container specific configurations? resources.volume, resources.image I think we should also go through all configuration names, ...
Opengraph URL: https://github.com/VirtualProgrammingLab/documentation/issues/4
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Container specific configuration","articleBody":"Why is the generic \"resources\" namespace used for (docker) container specific configurations? resources.volume, resources.image\r\n\r\nI think we should also go through all configuration names, currently they are all namespaced with the old phases names from viplab 2. I created the namespaces because I needed a mapping from the old config to the new configuration options in the websocket-api. But now as we completely dropped the support for the old format, we don't need the namespaces in this form, we can look for better names for the configuration options.","author":{"url":"https://github.com/Legion2","@type":"Person","name":"Legion2"},"datePublished":"2020-05-14T16:23:36.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/4/documentation/issues/4"}| 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:574db921-ac22-9c31-2c91-45990ee1538e |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | D502:307977:1CB73C:2549FF:698132CB |
| html-safe-nonce | aff8da48d267ae524c564e883bce19acba3ec3f583127af024fd9ef4e1671211 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJENTAyOjMwNzk3NzoxQ0I3M0M6MjU0OUZGOjY5ODEzMkNCIiwidmlzaXRvcl9pZCI6Ijg3NzE2MTE2NTQ1NTYyOTk5NzkiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | a4585ba4c7686d05669e6da3b797afb705fc812a6a75825aaf6157bca5249227 |
| hovercard-subject-tag | issue:618364955 |
| 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/VirtualProgrammingLab/documentation/4/issue_layout |
| twitter:image | https://opengraph.githubassets.com/158041b9719d1d3211008e04b1ca8decd18758ea8e0610e920d40d4a12d6dad0/VirtualProgrammingLab/documentation/issues/4 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/158041b9719d1d3211008e04b1ca8decd18758ea8e0610e920d40d4a12d6dad0/VirtualProgrammingLab/documentation/issues/4 |
| og:image:alt | Why is the generic "resources" namespace used for (docker) container specific configurations? resources.volume, resources.image I think we should also go through all configuration names, currently ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | Legion2 |
| hostname | github.com |
| expected-hostname | github.com |
| None | 39fe8101494cbb823c09b619b68c80cd4d05ab7279997038dbe06bb91608abe1 |
| turbo-cache-control | no-preview |
| go-import | github.com/VirtualProgrammingLab/documentation git https://github.com/VirtualProgrammingLab/documentation.git |
| octolytics-dimension-user_id | 61320153 |
| octolytics-dimension-user_login | VirtualProgrammingLab |
| octolytics-dimension-repository_id | 259589868 |
| octolytics-dimension-repository_nwo | VirtualProgrammingLab/documentation |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 259589868 |
| octolytics-dimension-repository_network_root_nwo | VirtualProgrammingLab/documentation |
| 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 | d5b34a4e4898b066c629879feb4b184bc471d6a7 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width