Garret Wassermann

Here's the announcement: https://blog.heroku.com/next-chapter

thank you for the offer @nickmccullum! DigitalOcean could be a solution, I'm not familiar with it as much, but appreciate the offer. I wasn't aware of Railway, thanks for the...

Thanks @Mte90 I saw the note at the bottom about open source. It wasn't clear to me that they'd still give dynos/database to open source, it sounded like it was...

I contacted Heroku at their open source email at the bottom and got: "We are in the process of finalizing the selection criteria and will contact you when we are...

Do you mean the demo site at: https://django-helpdesk-demo.herokuapp.com/? It is currently running the latest stable release (0.4.1) on Django 3.2. I do agree the demo script in the repo is...

Oh I see. Yes that's old file, the comments refer to Django 1.1 docs but it does work for newer versions of Django. The latest version of Django gets installed...

This is definitely worth exploring but will require some significant code changes I think. Will put it on the list for a future major version. Thanks for the suggestion!

Probably a good idea to work toward! For now I don't think our permissions system allows it.

That setting lets all users basically act like staff and update any ticket. From the docs (`settings.rst`): > Set to True to allow any authenticated user to manage tickets. >...

Is Pinax not compatible with django-allauth? I would say that's an oversight then, not intended to prevent other user management. If it's a label conflict I imagine we can rename...