[Feature Request] Allow for non-interactive createsuperuser

Is your feature request related to a problem? Please describe.

When deploying Evennia in a test environment where the DB gets wiped on each deploy, it would be nice if I could specify the super user creds using environmental variables.

Describe the solution you’d like

This might be an anti-pattern, so I’m interested in other’s opinion, but could we do something like the following?

def create_superuser():
    """
    Create the superuser account

    """
    print(
        "\nCreate a superuser below. The superuser is Account #1, the 'owner' "
        "account of the server. Email is optional and can be empty.\n"
    )
    from os import environ
    if ("DJANGO_SUPERUSER_USERNAME" in environ) and ("DJANGO_SUPERUSER_EMAIL" in environ):
        username = environ["DJANGO_SUPERUSER_USERNAME"]
        email = environ["DJANGO_SUPERUSER_EMAIL"]
        django.core.management.call_command("createsuperuser", "--noinput",
                                            "--username=" + username,
                                            "--email=" + email, interactive=False)
    else:
        django.core.management.call_command("createsuperuser", interactive=True)

    if "DJANGO_SUPERUSER_PASSWORD" in environ:
        password = environ["DJANGO_SUPERUSER_PASSWORD"]
        from evennia.accounts.models import AccountDB
        u = AccountDB.objects.get(username=username)
        u.set_password(password)
        u.save()

Of course you could have the username without the email, as the email is optional. Let me know if this seems reasonable and can create a PR.

Describe alternatives you’ve considered

I could be missing something but the alternative seems to be to type in the information manually whenever setting up a new DB.

Additional context

N/A

[Griatch]

@srmeier, @jerryaldrichiii Sorry for not getting back to you on this before now. This looks like a good idea. Between the two solutions offered here I think @srmeier’s is likely the cleanest one; it should work also for those wanting to use docker (you can just pass the envvars into the docker if so desired).

I’d be interested in a PR against develop branch for this one 👍.

[srmeier]

@srmeier, @jerryaldrichiii Sorry for not getting back to you on this before now. This looks like a good idea. Between the two solutions offered here I think @srmeier’s is likely the cleanest one; it should work also for those wanting to use docker (you can just pass the envvars into the docker if so desired).

I’d be interested in a PR against develop branch for this one 👍.

No problem, will make changes and PR for review.