django-currentuser | Conveniently store reference to request user | Caching library

by PaesslerAG Python Version: 0.5.3 License: BSD-3-Clause

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | django-currentuser Summary

django-currentuser is a Python library typically used in Server, Caching applications. django-currentuser has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can install using 'pip install django-currentuser' or download it from GitHub, PyPI.

Conveniently store reference to request user on thread/db level.

Support

Quality

Security

License

Reuse

Support

django-currentuser has a low active ecosystem.

It has 96 star(s) with 19 fork(s). There are 11 watchers for this library.

It had no major release in the last 12 months.

There are 7 open issues and 15 have been closed. On average issues are closed in 48 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of django-currentuser is 0.5.3

Quality

django-currentuser has 0 bugs and 2 code smells.

Security

django-currentuser has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

django-currentuser code analysis shows 0 unresolved vulnerabilities.

There are 7 security hotspots that need review.

License

django-currentuser is licensed under the BSD-3-Clause License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

django-currentuser releases are available to install and integrate.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

django-currentuser saves you 204 person hours of effort in developing the same functionality from scratch.

It has 502 lines of code, 36 functions and 17 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed django-currentuser and discovered the below as its top functions. This is intended to give you an instant insight into django-currentuser implemented functionality, and help decide if they suit your requirements.

Write the test suite
Return a matrix of tox code
Return the test command to run
Setup python
Parse tox output
Extracts the list of installed python versions

Get all kandi verified functions for this library.

django-currentuser Key Features

No Key Features are available at this moment for django-currentuser.

django-currentuser Examples and Code Snippets

No Code Snippets are available at this moment for django-currentuser.

Community Discussions

Trending Discussions on django-currentuser

Django ManifestStaticFilesStorage + DEBUG = False gives error in uploaded files: They don't show

QUESTION

Django ManifestStaticFilesStorage + DEBUG = False gives error in uploaded files: They don't show

Asked 2020-May-20 at 20:47

I have a problem and I will do the best to explain it, to see if you can help me out.

CONTEXT

I have a system running in a test server, which is set up like a production environment in order to test my code before merging to master and give the go to the production server provider of my client to update the code. This means it runs in DEBUG = False. All good, all perfect for months.

I decided to activate the ManifestStaticFilesStorage setting in order to have a hash number added in my static files, I've used it before and it's a good way to break cache rules when updating files (like CSS rules that refuse to load). There is an issue with cache that may be solvable messing around with the server but that's not an option in this case.

Everything went smoothly:

No issues in collectstatic other than a few missing static files (already solved)
Static files loaded perfectly

BUT...

THE PROBLEM

This system manages content (images, audio files and custom fonts). When I activated the ManifestStaticFilesStorage setting, all uploaded files started to throw 404 errors (and some occasional 500 error) in the server access log. Meaning, they look like this:

You can see the broken image icon but you can also see the background colores of each square (color which is injected by JS because it can be customized in the custom CMS). These images are uploaded in the CMS and they live in the media folder configured in the settings file.

Of course, if I go to DEBUG = True, everything gets fixed (come on! -.-). I went and recreated production enviroment in local, same issue: DEBUG = False bad, DEBUG = True works

THOUGHTS

404 means the file is not there. Guess what? it's there, they all are
The occasional 500 means permissions. Well, I haven't changed the permissions. Also, permissiones where the same. Also, I'm using WebFaction, it handles all that for me
Console in browser says network error. In the Network tab it doesn't even show the 404 errors or the few 500 that may appear
Broken DB? Nope. Besides, if it were broken, DEBUG = True would fail
Apache error log? Nothing to show for. The access log shows the access errors, meaning errors on file that are correctly placed

So, I ran out of ideas. Maybe someone out there has the answer, I hope so. I will still be trying to solve it but I can use the help, please.

RELEVANT CODE

storage.py

...

ANSWER

Answered 2020-May-20 at 20:47

Well, after hitting my head to the wall a lot, a good night sleep and fresh ideas, I found the problem. It was the silliest thing ever, as usual.

If you can see in the settings.py, the MEDIA_URL is set to /media/. Normally, this wouldn't be a problem in an Apache server but in WebFaction, it turned out to be the culprit of my headache.

For those who don't know, WebFaction obliges you to create apps for everything: Python env, PHP env, Static env, WordPress, Joomla, etc. By creating an app, you have to assing a unique path inside the Website definition, which is a set of apps running under a given domain, so all apps have paths under the same domain and you don't have to modify (in most cases) the httpd.conf file.

I have an app for the Django code and another app for the static files, under the domain static/. In the local_settings.py, you can see that the MEDIA_ROOT is inside this static path.

In a regular Apache deploy, you just assign the /media/ URL to the path and that's it. In WebFaction, given that there is no static app for using the media/, the MEDIA_URL variable has to have static/media as assigned value when switching to DEBUG = False.

Just to remember: DEBUG = False make Django stop serving the static files and leave that entirely to the server where is deployed. So, in DEBUG = True, it didn't matter which was the media URL because Django is smart enough to see past that. But when I made the switch to DEBUG = False, it naturally failed.

Silly me, but well, this is how we learn.

Regards.

Source https://stackoverflow.com/questions/61860606

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install django-currentuser

You can install using 'pip install django-currentuser' or download it from GitHub, PyPI.
You can use django-currentuser like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: