-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathdevcontainer.json
More file actions
97 lines (92 loc) · 3.66 KB
/
Copy pathdevcontainer.json
File metadata and controls
97 lines (92 loc) · 3.66 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
// https://github.com/microsoft/vscode-dev-containers/tree/v0.224.2/containers/docker-existing-docker-compose
{
<<<<<<< Updated upstream
"name": "objecscript-docker-template devcontainer",
=======
"name": "intersystems-iris-dev-template devcontainer",
>>>>>>> Stashed changes
// Use the same recipe as creates the container we use when working locally.
"dockerComposeFile": [
"../docker-compose.yml"
],
"service": "iris",
"workspaceFolder": "/home/irisowner/dev",
<<<<<<< Updated upstream
"customizations": {
"vscode": {
// This provides the elements of the connection object which require different values when connecting to the workspace within the container,
// versus those in .vscode/settings.json which apply when operating locally on the workspace files.
// We define and use a `server` so that (a) a user-level `objectscript.conn.server` properly doesn't override us, and (b) so InterSystems
// Server Manager can also be used.
"settings": {
"objectscript.conn" :{
"server": "devcontainer",
"active": true
},
"intersystems.servers": {
"devcontainer": {
"username": "SuperUser",
"password": "SYS",
"webServer": {
"scheme": "http",
"host": "127.0.0.1",
"port": 52773
}
}
},
"python.defaultInterpreterPath":"/usr/irissys/bin/irispython"
},
// Add the IDs of extensions we want installed when the container is created.
// Currently (March 2022) `intersystems.language-server` fails to run within the container (alpine platform).
// Issue is probably https://github.com/intersystems/language-server/issues/185 and/or https://github.com/intersystems/language-server/issues/32
// Crash gets reported to the user, after which `intersystems-community.vscode-objectscript` falls back to
// using its TextMate grammar for code coloring.
"extensions": [
"ms-python.python",
"ms-python.vscode-pylance",
"intersystems-community.vscode-objectscript",
"intersystems.language-server",
"intersystems-community.servermanager",
"ms-vscode.docker"
]
}
}
=======
// This provides the elements of the connection object which require different values when connecting to the workspace within the container,
// versus those in .vscode/settings.json which apply when operating locally on the workspace files.
// We define and use a `server` so that (a) a user-level `objectscript.conn.server` properly doesn't override us, and (b) so InterSystems
// Server Manager can also be used.
"settings": {
"objectscript.conn" :{
"server": "devcontainer",
"active": true,
},
"intersystems.servers": {
"devcontainer": {
"username": "SuperUser",
"password": "SYS",
"webServer": {
"scheme": "http",
"host": "127.0.0.1",
"port": 52773
},
},
},
"python.defaultInterpreterPath":"/usr/irissys/bin/irispython"
},
// Add the IDs of extensions we want installed when the container is created.
// Currently (March 2022) `intersystems.language-server` fails to run within the container (alpine platform).
// Issue is probably https://github.com/intersystems/language-server/issues/185 and/or https://github.com/intersystems/language-server/issues/32
// Crash gets reported to the user, after which `intersystems-community.vscode-objectscript` falls back to
// using its TextMate grammar for code coloring.
"extensions": [
"ms-python.python",
"ms-python.vscode-pylance",
"intersystems-community.vscode-objectscript",
"intersystems.language-server",
"intersystems-community.servermanager",
"ms-vscode.docker"
],
>>>>>>> Stashed changes
}