#django

b0nn: almost same; ERROR: extension "postgis" has no installation script nor update path for version "2.4.1"

sphrak: ok, so it sounds like the install hasn't taken place for whatever reason

b0nn: thats odd because the postgis.control file is there

above my paygrade I'm afraid

postgresql-x.x, postgresql-x.x-postgis, postgresql-server-dev-x.x, python-psycopg2 (

^^ all those installed as per the django docs?

im on alpinelinux, they are named differently but yes I have em

my only advice would be to ask on #postgres

good idea, ill do that. thanks b0nn :-)

because, as I say, it's gone past my small vessel of knowledge

yes, Ive asked them so lets see what they have to say

doismellburning: What's ZK? I'm kindof new to k8s stuff.

NfNitLoop: Zookeeper

aaah. No, I don't think we've got that set up. (I assume it's not built-in?)

...sorry, I was thinking of Kafka that needs ZK to run, not k8s

love it

can anyone help? https://www.reddit.com/r/django/comments/7myive...

I can't remember the right term, but you don't want (just) "payment processing", you want like

paid-user lifecycle management or something

oh

sounds like you want something handling allll of that, on top of "here's a payment prompt for something"

Hey, I'm trying to understand permissions. They are just models like User and Groups, right? It's just a name and then everywhere you want to restrict something you have to do something like 'does this user have this permission, if so do this, if not do this'

Except with models, as I understand it you set something in the model itself and then it restricts "automatically" , but outside of that, there's nothing magical happening, right?

It's just a name

And then you use it like a boolean

And users and Groups have FK to that permission

Crystalk3: yes, it's just a name... and ayou can add as many as you like

Groups are to help with bulk assignment and management of permissions

FunkyBob: As many what?

Permissions to a user/group?

you can define as many permissions as you like

OK

and, yes, assign as many as you wish to each user/group

Next question

What on earth is 'content_type' ? It says 'Required' in https://docs.djangoproject.com/en/1.11/ref/cont... but I don't understand what any of 'A reference to the django_content_type database table, which contains a record for each installed model.' means

ok, so for each model in your project, an entry is made in the ContentTypes table

this is how teh system knows which model a permission is related to

[a slightly broken concept, in truth, but it's how the system has lived for ~15 years now]

But is this field in permissions like automatically filled or do I have to put something there?

you don't normally create a Permission instance yourself

put your list there, and the permissions will be automagically created for you

of course, yes, you _can_ create them yourself... in which case yes you need a ContentTyp record to relate there

What list?

In this case it's a permission for a view

are you not reading any of the links I give you?

To use with the permission_required decorator

So I guess I have to create it myself?

https://docs.djangoproject.com/en/2.0/ref/model... <-0-- HERE this list you can specify on your Model.Meta

permission required deecorator just wants the label for the permissions

Yeah the codename or name but I have to create it first right?

no, Django can create it for you, as I said

I'm sorry, but I'm not understanding

on every model you define

you can specify a list of permissions you want for that model

The link you sent me is about the permissions Meta option on a model, right?

and django will create thos epermissions for you

Well, I didn't know that, I thought you had to create the permissions manually and then reference them in a Meta option in the model

It's good to know

Thank you

However

As I said, I'm talking about a permission I need for the permission_required decorator. It's not related to any model so how would I specify a list of permissions for that model, so that django creates it for me, as you said?

it's a limitation of the default djangopermissions model that all permissions must be related to a model

01:33 <+FunkyBob> [a slightly broken concept, in truth, but it's how the system has lived for ~15 years now]

if you need more flexibility, use @user_passes_test or something

With djangopermissions you mean django.contrib.auth.models.Permission, correct?

it's a shame... if they just let content_type be null on Permission....

Crystalk3: correct

But then how do I use the permission_required decorator

?

...

I sound like a broken record, I'm sorry

the same as always?

by not using it ;)

Crystalk3: which step of the docs on using it is confusing you?

OOF