Conversation
brianhelba
force-pushed
the
resonant-upgrade
branch
4 times, most recently
from
ced4f53 to
6a945a5
Compare
| ```sh | ||
| ./manage.py migrate | ||
| ./manage.py createsuperuser | ||
| ./manage.py loaddata species |
There was a problem hiding this comment.
Is this still necessary, or does the migration handle it?
| ```bash | ||
| docker compose run --rm -v /path/to/wav/files:/data django ./manage.py importRecordings /data | ||
| ```sh | ||
| ./manage.py importRecordings /data |
There was a problem hiding this comment.
Modifying the volume mounts like this isn't really compatible with dev containers. Of course, it's possible to modify the Docker Compose files and then restart the whole stack, but I think the better approach is just to hardlink the files from their host filesystem into the repo.
@BryonLewis Can you test if hardlinks work, then we can update these docs accordingly?
|
@BryonLewis @naglepuff This is ready for testing and review. Any feedback is welcome. |
brianhelba
force-pushed
the
resonant-upgrade
branch
from
6a945a5 to
3d70efa
Compare
|
I just rebased this and bumped it with an upstream patch version. |
| "requireLocalPort": true, | ||
| "onAutoForward": "silent" | ||
| }, | ||
| "8080": { |
There was a problem hiding this comment.
Doesn't work unless we bind to 0.0.0.0.
| "justMyCode": false | ||
| }, | ||
| { | ||
| "name": "Pytest: Debug", |
There was a problem hiding this comment.
Test breakpoints weren't working for Bryon for some reason.
1 participant
No description provided.