Package: django-mimicry
Mimicry Django AppGeneral DetailsDescriptionThe Mimicry Django app provides developers with a robust toolset to simulate user experiences within their web applications. By impersonating a specific user or even an anonymous user, developers can observe user experiences firsthand, enabling easier debugging, testing, and understanding of user interfaces and functionality.FeaturesPrivate Tags Functionality: Safeguard sensitive content in templates with{% private %}and{% privateblock %}tags.Fully Simulated Sessions: Impersonate any user in the system, including anonymous users, with a complete session simulation.Transparency with Notifications & Logs: Stay informed about all simulation activities through comprehensive notifications and logs.Customizable with Settings: Tweak the app behavior according to project requirements. It's important to note that this app should not be used in production environments due to potential security concerns.Extendable Template with UI: An aesthetically pleasing user interface for switching users is available in the mimicry_base.html template, which can be extended by any template in your project.Setup InstructionsInstall the App:pip install django-mimicryAdd the App:
Include 'simulateuser' in your INSTALLED_APPS setting.INSTALLED_APPS=[...'mimicry',...]Add the URLs:
Ensure that you add the app's URL configurations to your project's urls.py:urlpatterns=[...path('mimicry/',include('mimicry.urls')),...]Middleware and Context Manager:
Ensure you add the necessary middleware and context manager for the app in the respective Django settings:MIDDLEWARE=[...'mimicry.middleware.MimicryMiddleware',...]TEMPLATES=[{...'OPTIONS':{'context_processors':[...'mimicry.context_processors.mimicry_context',...],},...},]Database Migrations:
After integrating the app, run:python manage.py makemigrations
python manage.py migrateUsageExtend the Mimicry Base Template:
In order to make use of the Mimicry features, you must decide which pages on your website should have the Mimicry UI on it. Any page that you want to be able to be viewed in a simulated session should be extending the mimicry_base.html template:{% extends 'mimicry/mimicry_base.html' %}

{% block headtitle %}
    My App Title
{% endblock %}
{% block extrahead %}
    Extra Head Content
{% endblock %}

{% block maincontent %}
    Actual Content
{% endblock %}Simulate User and Session Data:
The Mimicry app, when set to do so will automatically set the request.user to be an authenticated version of the user you are simulating. Or if you chose unauthenticated, it will simulate request.user as an unauthenticated user.
The app will also create an entirely separate session for the simulated user. When you access request.session of a simulated session, it will be the session of the simulated user and not the real user. You will always be able to access the real user by referencing request.real_user.
The Mimicry app can switch back to the user's real session and real user data by the user disabling the simulation in their UI or by logging out. Simulated sessions will also expire at a set time (by default 3600 seconds).Simulate User Logs:
For the purposes of ensuring the security and safety of your users. Superusers are able to see in their Django Admin Site a log of all simulated sessions and all actions taken while in simulation. Please be aware that these logs are set to delete after a set amount of time (by default 14 days) in order to ensure that they do not take up too much space in your database.Simulate User Notifications:
Mimicry is set to notify users by email when someone uses the Mimicry feature to simulate their account. This is meant to ensure transparency for your users. The default templates for these emails can be overwritten. Please read more about overwriting templates in Django documentation for more details.Set Certain Information as Private:
While in simulation mode, it might be the case that certain information is deemed private and only for the real user to see. When encountering such cases, you can make use of the private tags to ensure that private information is only seen by the real user.<p>{% private 'Some Content that should be private' %}</p>{% privateblock %}<p>Some Content that should be private</p><p>Some Content that should be private</p><p>Some Content that should be private</p>{% endprivateblock %}ConfigurationMimicry has many different settings that you can control to ensure that your Mimicry experience is exactly the solution your project needs.Enable or Disable Mimicry:
By default, Mimicry is enabled. This means that the UI and entire feature set supplied by Mimicry is working as designed. However, you can disable it. To disable Mimicry, you simply need to have the following line in your settings file and set it to False.
We highly recommend against leaving Mimicry enabled in production.ENABLE_MIMICRY:bool=TrueEnable or Disable Simulate User Notifications:
By default, Simulate User Notifications are enabled. This means that Mimicry will notify an end user when they are being simulated. This can be toggled with the following setting but is highly recommended against for security purposes.ENABLE_SIMULATE_USER_NOTIFICATIONS:bool=TrueSet Authentication Backend:
If you use an authentication backend other than the default backend, you should alter the Mimicry backend with the path for the one that it should use. By default, it is set to use the django default authentication backend. However, if you use different backends, it might be necessary to make Mimicry use the correct one.MIMICRY_AUTHENTICATION_BACKEND:str='django.contrib.auth.backends.ModelBackend'Restrict Actions of Staff Members in Simulation Mode:
By default, Mimicry only allows GET and HEAD requests to be done in simulation mode. This is for security and safety purposes. However, you can change this by toggling the setting:ONLY_ALLOW_SIMULATED_GET_AND_HEAD_REQUESTS:bool=TrueSet Custom Private Replacement Text:
By default, Mimicry replaces all text in private tags with 'HIDDEN FOR USER PRIVACY PURPOSES'. However, you can change that using the following setting:PRIVATE_CONTENT_REPLACEMENT:str='HIDDEN FOR USER PRIVACY PURPOSES'Set Custom Session Settings:
By default, Mimicry sets all simulated sessions to last for a maximum of 3600 seconds. It also automatically deletes all simulated sessions and simulated session actions after 14 days. You can toggle those settings as follows:SIMULATED_SESSION_EXPIRY:int=3600SIMULATED_SESSION_RETENTION:int=14Set Who Can See and Use Mimicry:
By default, Mimicry is set to be enabled for all users who have the is_staff attribute as True. However, you can change this by using any bool attribute of your user model. You can create your own for maximum integration. You can toggle the following setting:MIMICRY_FEATURE_CONTROL_CONDITION:str='is_staff'Set Who Can Simulate Which Users:
By default, MIMICRY is set to allow all staff members to simulate all users. However, you can customize this and make any users be able to simulate any users. This setting works based on attributes, and it works in order lists. Mimicry will look for the setting MIMICRY_PERMISSIONS and will go through it in order. This setting should contain a list of dictionaries. Each dictionary should contain two key, value pairs. The first key value pair should be SIMULATED_USER_ATTRIBUTE and a bool attribute in your user model. the second pair should be REAL_USER_ATTRIBUTE and a bool attribute of your user model. When checking if a user has permissions to simulate any given user, Mimicry will go through the list and find the first SIMULATED_USER_ATTRIBUTE that the simulated user meets as true and then it will check the real user attribute for that setting for the real user and if it returns as true, permission will be granted, otherwise it will be denied.:MIMICRY_PERMISSIONS:list[dict[str,str]]=[{"SIMULATED_USER_ATTRIBUTE":"is_active","REAL_USER_ATTRIBUTE":"is_staff"}]ContributingAs this is an open-source project hosted on GitHub, your contributions and improvements are welcome! Follow these general steps for contributing:Fork the Repository:
Start by forking the main repository to your personal GitHub account.Clone the Forked Repository:
Clone your forked repository to your local machine.git clone https://github.com/YidiSprei/DjangoMimicry.gitCreate a New Branch:
Before making any changes, create a new branch:git checkout -b feature-nameMake Your Changes:
Implement your features, enhancements, or bug fixes.Commit & Push:git add .
git commit -m "Descriptive commit message about changes"
git push origin feature-nameCreate a Pull Request (PR):
Go to your forked repository on GitHub and click the "New Pull Request" button. Make sure the base fork is the original repository, and the head fork is your repository and branch. Fill out the PR template with the necessary details.Remember to always be respectful and kind in all interactions with the community. It's all about learning, growing, and helping each other succeed!CreditsDeveloped with ðŸ’™ by Yidi Sprei. We thank all the contributors and the Django community for their support and inspiration.