List for cgit developers and users
 help / color / mirror / Atom feed
From: melmothx at gmail.com (Marco Pessotto)
Subject: Running CGit with user owning the repository
Date: Wed, 12 Dec 2018 20:11:14 +0100	[thread overview]
Message-ID: <87o99qsgq5.fsf@universe.krase.net> (raw)


Hi there,

this is going to be a dumb question, but are there major concerns about
running CGit with the same user owning the repository? Ok, not
super-optimal, but is that acceptable?

I think CGit avoids to even touch the repo is serving and it shouldn't
write on it, but I'd like to know what you think about it.

The rationale behind this question is that I'm embedding cgit in an
application (amusewiki.org/git) and the setup would be simplified a lot
without the need of another service just for this. If you encourage the
user separation, I'll keep the things as they are.

Thanks in advance

Best wishes

--
Marco


             reply	other threads:[~2018-12-12 19:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 19:11 melmothx [this message]
2018-12-13 20:24 ` konstantin
2018-12-14 10:24   ` melmothx

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o99qsgq5.fsf@universe.krase.net \
    --to=cgit@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).