| Message ID | 1472155412-7666-2-git-send-email-f.fainelli@gmail.com |
|---|---|
| State | Superseded |
| Headers | show |
> +## Django administrative console > + > +In order to access the administrative console at `/admin`, you need at least > +one user account to be registered and configured as a "staff" account to access > +the Django administrative console. This can be achieved by altering the > +`auth_user` table and setting your favorite user entry to have `is_staff` set > +to `1`. Once done, such user can add projects which are required for email > +delivery to operate correctly. > + > +Once the administrative console is accessible, you would want to configure your > +different sites and their corresponding domain names, which is required for the > +different emails sent by patchwork (registration, password recovery) as well as > +sample `pwclientrc` files provided by your project's page. > + Hmm. Wouldn't it be easier to do this with 'python[3] manage.py createsuperuser'? (or just 'createsu' if you're using docker or vagrant) Regards, Daniel > ## Incoming Email > > Patchwork is designed to parse incoming mails which means you need an address > -- > 2.7.4 > > _______________________________________________ > Patchwork mailing list > Patchwork@lists.ozlabs.org > https://lists.ozlabs.org/listinfo/patchwork
On 26 Aug 12:12, Daniel Axtens wrote: > > > +## Django administrative console > > + > > +In order to access the administrative console at `/admin`, you need at least > > +one user account to be registered and configured as a "staff" account to access > > +the Django administrative console. This can be achieved by altering the > > +`auth_user` table and setting your favorite user entry to have `is_staff` set > > +to `1`. Once done, such user can add projects which are required for email > > +delivery to operate correctly. > > + > > +Once the administrative console is accessible, you would want to configure your > > +different sites and their corresponding domain names, which is required for the > > +different emails sent by patchwork (registration, password recovery) as well as > > +sample `pwclientrc` files provided by your project's page. > > + > > Hmm. Wouldn't it be easier to do this with 'python[3] manage.py createsuperuser'? (or > just 'createsu' if you're using docker or vagrant) I like the idea but Daniel is correct: the createsuperuser command is the way to do this. Could you document this approach instead, please? Stephen
diff --git a/docs/deployment.md b/docs/deployment.md index 1d9ca8ea5b1c..32732244d989 100644 --- a/docs/deployment.md +++ b/docs/deployment.md @@ -336,6 +336,20 @@ Finally, browse to the instance using your browser of choice. You may wish to take this opportunity to setup your projects and configure your website address (in the Sites section of the admin console, found at `/admin`). +## Django administrative console + +In order to access the administrative console at `/admin`, you need at least +one user account to be registered and configured as a "staff" account to access +the Django administrative console. This can be achieved by altering the +`auth_user` table and setting your favorite user entry to have `is_staff` set +to `1`. Once done, such user can add projects which are required for email +delivery to operate correctly. + +Once the administrative console is accessible, you would want to configure your +different sites and their corresponding domain names, which is required for the +different emails sent by patchwork (registration, password recovery) as well as +sample `pwclientrc` files provided by your project's page. + ## Incoming Email Patchwork is designed to parse incoming mails which means you need an address
Provide a few hints about how to get initial access to the django admin console as well as a few essential configuration hints. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> --- docs/deployment.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+)