https://github.com/anthonyshibitov/netdis
Web based binary analysis
https://github.com/anthonyshibitov/netdis
assembly binary-analysis c exploit-development forensics python reverse-engineering webapp
Last synced: 25 days ago
JSON representation
Web based binary analysis
- Host: GitHub
- URL: https://github.com/anthonyshibitov/netdis
- Owner: anthonyshibitov
- Created: 2024-07-17T22:42:24.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2024-11-21T00:33:27.000Z (5 months ago)
- Last Synced: 2025-03-31T17:17:14.069Z (about 1 month ago)
- Topics: assembly, binary-analysis, c, exploit-development, forensics, python, reverse-engineering, webapp
- Language: JavaScript
- Homepage: https://netdis.org/
- Size: 3.97 MB
- Stars: 84
- Watchers: 2
- Forks: 11
- Open Issues: 0
-
Metadata Files:
- Readme: readme.MD
Awesome Lists containing this project
README
# Netdis
## Web based binary analysis
Netdis is an open-source binary analysis tool powered by Ghidra. Upload files for disassembly, decompilation, control flow graphs and more, all in your browser.
## [https://netdis.org/](https://netdis.org/)
## Deployment configuration
The address of the backend needs to be specified in the respective `frontend/.env.vite.dev` and `frontend/.env.vite.prod` files, depending on the type of deployment. For development, this can typically be left at `http://localhost:8000/`. When deploying to production, this must point to the address of the backend. Additionally, the Vite files are built using this environment variable, so it may not reflect until the build has completed and the built files are available in the `frontend/dist/` directory.
The remaining environment variables are defined in the `.env.dev` and `.env.prod` files. When deploying to production, the `DJANGO_ALLOWED_HOSTS` and `CORS_ALLOWED_ORIGINS` must contain the address of the frontend, which is typically just the host, as it is being served via nginx on port 80.
### Deployment commands
Deploy for development:
`docker-compose -f docker-compose.yml -f docker-compose-dev.yml up --build`
Deploy for production:
`docker-compose -f docker-compose.yml -f docker-compose-prod.yml up --build`
### Database Migrations
Between changes to any Django models, old PostgreSQL volumes will need to be deleted. Otherwise, there will be errors to non-existant fields.
`docker volume rm netdis_postgres_data`