1. django_hg : authentication throught django is OK

    This is an important step in django_hg build has been reached : authentication — HTTP(S) only — of clone, pushand pullcommands sended by Mercurial is completely handled by django.

    There’s two majors workflows:

    • For public projects (with anonymous_access sets to True), clone et pull are anonymous. push requires an authentication, the user must have the read/write permission for the projet. This schema is often used for open-source projects.
    • For private projects (anonymous_access sets to False), all commands require to have read/write permission for the projet.

    In this context, read permission only allow to display project in the browser. I will rename it into web view. This change won’t have any impact on the software, but it will clarify things.

    In the next weeks, I will work on the UI, which leads me to see how CSS and images are handled in django reusable apps, like those found in pinax [en]. I also need to complete unavailable functionalities, like diff, branches, …

    Afterwards, I think I will add a mini bugtracker, so django_hg will be a simple yet complete tool.

    Text
    5 months ago