Services #25
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: data.coop/membersystem#25
Loading…
Reference in a new issue
No description provided.
Delete branch "services"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Dette PR handler om at få en måde hvorpå medlemmer kan få adgang til de forskellige services vi udbyder.
ad6564b510
to6e2ed21f67
@ -142,0 +165,4 @@
)
def __str__(self) -> str:
return f"{self.user} - {self.service}"
Just wanna say that I've seen this WRT the Membership and MembershipType definitions. I think this will work fine in combination. I have some ideas etc.. but fundamentally, this doesn't need to change 👍
There will be a new model Product and Order that are relevant for charging services, but we can probably figure out how they are associated with services... I like the idea of matching a service with some well-known string.
@ -142,0 +154,4 @@
),
)
user = models.ForeignKey("auth.User", on_delete=models.PROTECT)
This is correct! 💯
Notable because there is also a Membership model.. however, memberships are renewed every year, and a user should be able to use the same services across different memberships.
How we handle "eligibility to a service" can happen later..
ce8d4bd228
tod82a91d710
WIP: Servicesto ServicesVERY NICE! Having this will make it possible to start adding ServiceRequests, then we can figure out what that means to UI.
(but I would only add a ServiceRequest model in order to auto-create the Matrix+Forgejo service request for new members)
@ -163,0 +172,4 @@
},
"PKCE_REQUIRED": False, # this can be a callable - https://github.com/jazzband/django-oauth-toolkit/issues/711#issuecomment-497073038
}
I don't know what this is :)
Yeah not sure yet either. It is a part of making the membersystem the SSO to login to services using OpenID Connect.
@ -81,3 +81,3 @@
{% comment %}
<li>
<a href="/services" class="{% active_path "services" "current" %}">
<a href="{% url "services:list" %}" class="{% active_path "services:list" "current" %}">
Instead of commenting it out, you could also do some
if user.is_superuser
?OH! Can you add Forgejo / Git?
One more thing: Services have a kind of "slug" that's used here: https://git.data.coop/data.coop/website/src/branch/main/content/services
Is the intention that it's the same slug we use in the public website? That'd be great, because then we can easily link content.
Yes - services also have slugs in the
services/services.py
module ;)Done!