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
The script is idempotent and can be run multiple times without issues.
50
-
51
-
The container was designed to be used for development with contracts repo at `/git/graphprotocol/contracts` and with `/git` mounted from the host by `docker-compose.yml`.
40
+
## Setup Instructions
52
41
53
-
### 2. Start the Dev Container
42
+
### Start the Dev Container
54
43
55
-
After creating the cache directories, you can start the dev container:
44
+
To start the dev container:
56
45
57
46
1. Open VS Code
58
47
2. Use the "Remote-Containers: Open Folder in Container" command
59
48
3. Select the repository directory (for example `/git/graphprotocol/contracts`)
60
49
61
50
When the container starts, the `project-setup.sh` script will automatically run and:
62
51
63
-
- Create package-specific cache directories
64
-
- Set up symlinks for package cache directories
65
52
- Install project dependencies using yarn
66
53
- Configure Git to use SSH signing with your forwarded SSH key
67
54
- Source shell customizations if available in PATH
@@ -87,11 +74,13 @@ These environment variables are needed for Git commit signing to work properly.
87
74
88
75
## Troubleshooting
89
76
90
-
If you encounter permission denied errors when trying to access directories, make sure you've run the `host-setup.sh` script on the host before starting the container:
77
+
### Cache Issues
91
78
92
-
```bash
93
-
sudo .devcontainer/host-setup.sh
94
-
```
79
+
If you encounter build or compilation issues that seem related to cached artifacts:
80
+
81
+
1.**Rebuild the container**: This will start with fresh local caches
82
+
2.**Clean project caches**: Run `yarn clean` to clear project-specific build artifacts
83
+
3.**Clear node modules**: Delete `node_modules` and run `yarn install` again
0 commit comments