Skip to content

structure.md

Latest commit

 

History

History
77 lines (63 loc) · 2.23 KB

structure.md

File metadata and controls

77 lines (63 loc) · 2.23 KB

Directory Structure Guide

This guide explains the recommended directory structure for organizing your OpenBullet configuration files and related documentation.

Recommended Project Structure

your-project/
├── configs/                 # Main configuration directory
│   ├── opk/                # OpenBullet .opk files
│   ├── loli/               # LoliScript .loli files
│   ├── anom/               # Anomaly .anom files
│   └── svb/                # SilverBullet .svb files
├── data/                   # Data files (wordlists, proxies, etc.)
│   ├── wordlists/
│   ├── proxies/
│   └── useragents/
├── results/                # Output results
├── logs/                   # Log files
└── docs/                   # Documentation
    ├── guides/
    └── examples/

File Organization Best Practices

Configuration Files

  • Group configs by format in separate subdirectories
  • Use descriptive filenames (e.g., login_facebook.opk)
  • Include version numbers for config iterations
  • Add comments in configs when possible

Data Files

  • Keep wordlists organized by type (usernames, passwords, emails)
  • Separate proxy lists by type (HTTP, SOCKS4, SOCKS5)
  • Maintain backup copies of important data files

Results and Logs

  • Create timestamped subdirectories for each run
  • Separate successful and failed results
  • Archive old logs to prevent disk space issues

Naming Conventions

Config Files

[purpose]_[target]_[version].[extension]
Examples:
- login_instagram_v2.opk
- checker_netflix_premium.loli
- brute_force_admin.anom
- multi_check_social.svb

Data Files

[type]_[description].[extension]
Examples:
- usernames_common.txt
- passwords_rockyou.txt
- proxies_http.txt
- useragents_mobile.txt

Backup and Version Control

  • Use Git for version control of your configs
  • Keep backups of working configs before modifications
  • Document changes in commit messages
  • Tag important config versions

Security Considerations

  • Never commit sensitive data (passwords, API keys) to version control
  • Use .gitignore to exclude sensitive files
  • Encrypt sensitive configuration data when possible
  • Regularly rotate proxy lists and user agents