hamel winglian commited on
Commit
2dc4310
1 Parent(s): 6d342b5

Add link on README to Docker Debugging (#1107)

Browse files

* add docker debug

* Update docs/debugging.md

Co-authored-by: Wing Lian <wing.lian@gmail.com>

* explain editable install

* explain editable install

* upload new video

* add link to README

* Update README.md

* Update README.md

* chore: lint

* make sure to lint markdown too

---------

Co-authored-by: Wing Lian <wing.lian@gmail.com>

Files changed (3) hide show
  1. .github/workflows/lint.yml +22 -0
  2. README.md +3 -0
  3. docs/debugging.md +2 -2
.github/workflows/lint.yml ADDED
@@ -0,0 +1,22 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ name: lint
2
+ on:
3
+ # check on PRs, and manual triggers
4
+ pull_request:
5
+ paths:
6
+ - '**.py'
7
+ - 'requirements.txt'
8
+ - '.github/workflows/*.yml'
9
+ - "*.md"
10
+ workflow_dispatch:
11
+
12
+ jobs:
13
+ pre-commit:
14
+ name: pre-commit
15
+ runs-on: ubuntu-latest
16
+ steps:
17
+ - uses: actions/checkout@v3
18
+ - uses: actions/setup-python@v4
19
+ with:
20
+ python-version: "3.9"
21
+ cache: 'pip' # caching pip dependencies
22
+ - uses: pre-commit/action@v3.0.0
README.md CHANGED
@@ -132,6 +132,9 @@ accelerate launch -m axolotl.cli.inference examples/openllama-3b/lora.yml \
132
  docker compose up -d
133
  ```
134
 
 
 
 
135
  <details>
136
 
137
  <summary>Docker advanced</summary>
 
132
  docker compose up -d
133
  ```
134
 
135
+ >[!Tip]
136
+ > If you want to debug axolotl or prefer to use Docker as your development environment, see the [debugging guide's section on Docker](docs/debugging.md#debugging-with-docker).
137
+
138
  <details>
139
 
140
  <summary>Docker advanced</summary>
docs/debugging.md CHANGED
@@ -182,7 +182,7 @@ style="border-radius: 10px; display: block; margin: auto;" width="560" height="3
182
 
183
  ## Debugging With Docker
184
 
185
- Using [official Axolotl Docker images](https://hub.docker.com/r/winglian/axolotl/tags) is a great way to debug your code, and is a very popular way to use Axolotl. Attaching VSCode to Docker takes a few more steps.
186
 
187
  ### Setup
188
 
@@ -218,7 +218,7 @@ Next, if you are using a remote host, [Remote into this host with VSCode](https:
218
 
219
  Next, select `Dev Containers: Attach to Running Container...` using the command palette (`CMD + SHIFT + P`) in VSCode. You will be prompted to select a container to attach to. Select the container you just created. You will now be in the container with a working directory that is at the root of the project. Any changes you make to the code will be reflected both in the container and on the host.
220
 
221
- Now you are ready to debug as described above (see [Debugging with VSCode](#debugging-with-vscode)).
222
 
223
  ### Video - Attaching To Docker On Remote Host
224
 
 
182
 
183
  ## Debugging With Docker
184
 
185
+ Using [official Axolotl Docker images](https://hub.docker.com/r/winglian/axolotl/tags) is a great way to debug your code, and is a very popular way to use Axolotl. Attaching VSCode to Docker takes a few more steps.
186
 
187
  ### Setup
188
 
 
218
 
219
  Next, select `Dev Containers: Attach to Running Container...` using the command palette (`CMD + SHIFT + P`) in VSCode. You will be prompted to select a container to attach to. Select the container you just created. You will now be in the container with a working directory that is at the root of the project. Any changes you make to the code will be reflected both in the container and on the host.
220
 
221
+ Now you are ready to debug as described above (see [Debugging with VSCode](#debugging-with-vscode)).
222
 
223
  ### Video - Attaching To Docker On Remote Host
224