How sarthakghere/file-encryptor works
Project Type and Purpose
• The project is a Django web application designed to encrypt and decrypt files using RSA and AES encryption.
• Key functionalities include RSA key pair generation, file encryption, file decryption, and file download.
• It leverages Django (with its MVC-like structure) alongside a cryptography library, and it uses SQLite for data persistence.
• The top-level “encryptor” directory contains the standard Django project files (settings, urls, wsgi/asgi) and the “manage.py” script.
• There are two prominent Django apps: “ui” and “util”. The “ui” app appears to cover user interfaces (templates, forms, views, and models related to handling file encryption/decryption workflows), while the “util” app seems to include additional functionality such as middleware and its own models.
• The presence of “db.sqlite3” confirms that the app uses SQLite as the database.
• In your structure, you have separate models modules in both “ui” and “util”, suggesting distinct data entities that may capture encryption keys, logging, or file metadata.
Final Touches
• Remember that even if the models are simple, capturing their relationships (if any exist) helps in understanding how encrypted file metadata, keys, or logs might be interconnected.