From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] intro'ing myself
Date: Wed, 9 Dec 2020 12:23:16 +0100 [thread overview]
Message-ID: <54f26d2b-dd9b-4f85-ae83-7c6260c26962@proxmox.com> (raw)
In-Reply-To: <5FCACA8A02000088000040E7@mail.comsolve.nl>
On 12/5/20 12:47 AM, Michael Honkoop wrote:
> Hi all,
>
> First of all nice to meet you,
Hi,
>
> As both a new participant on the list aswell as someone who is trying to step in/up/learn-by-doing i expect my future posts to contain a lot of questions and struggles trying to find a/the structure.
>
no problem, please ask away.
We try to answer question as good as possible, to a reasonable extent.
Please make sure to read the developer docs[0], they also
contain a link to the build instructions.
> My (personal) goal is to enhance skills and produce a working oauth extension, which i have seen was already requested back in 2017.
Great you want to tackle that.
A good starting point would be probably the 'pve-access-control'
package/repository[1]
Also it would be nice if you could outline your ideas/use-cases before
actually starting to write code, so that we can catch
design problems early.
>
> As PVE as product means multiple disciplines i hope i can be directed in the right direction, as currently i see the code (individually (per-file)), but i am lacking the linkage.
i am not sure i understand the question.
pve is split into many packages, most of them have their own
git repository[2]
from those repositories, the packages get built and installed.
most code of pve is perl, and in debian
you can find the installed perl packages in /usr/share/perl5
and PVE specific code in /usr/share/perl5/PVE
>
> I mean an extension of a base something i can understand/comprehend, but some stuff like schema seems to be burried deep somewhere and havent figured out how to add stuff.
>
the jsonschema is a complicated beast ;)
but to use it you do not have to look at it directly,
better to look at how we use it
in many packages there is a PVE/API2/ folder
which contains the api endpoint definitions
those can serve as examples
hope this helps :)
kind regards
Dominik
0: https://pve.proxmox.com/wiki/Developer_Documentation
1: https://git.proxmox.com/?p=pve-access-control.git;a=summary
2: https://git.proxmox.com
prev parent reply other threads:[~2020-12-09 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 23:47 Michael Honkoop
2020-12-09 11:23 ` Dominik Csapak [this message]
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=54f26d2b-dd9b-4f85-ae83-7c6260c26962@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.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