This page covers the details on how to obtain and use your personal space on fedorapeople.org , which is a site where Fedora contributors can upload files for sharing out with the world. It is perfect for uploading specfiles, srpms, patches, personal repository etc, etc.
- Do NOT distribute anything on fedorapeople.org that Fedora itself cannot distribute for legal reasons. Nothing on the ForbiddenItems list or otherwise non distributable by Fedora.
- Do NOT upload your private .ssh keys. While Fedora Infrastructure Team works hard on keeping the servers secure, break ins will happen and private keys uploaded can be downloaded and brute-forced easily these days. Private .ssh keys if found during an audit will be deleted.
Accessing Your fedorapeople.org Space
- You need an active Fedora account
- You must be sponsored in at least one group that is not a cla* group.
- You need to generate a ssh key (ssh-keygen -t rsa).
- Upload that ssh key into your Fedora account. To upload, visit this link and select your key file using the Public RSA SSH key field. Normally your key is stored in your home directory under .ssh/id_rsa.pub. The ssh key gets activated an hour after you upload it.
- To connect, use the ssh key you uploaded into your Fedora account:
ssh -i ~/.ssh/id_rsa <your_username>@fedorapeople.org
This step can also be done via Fedora account.
- While logged in, click on "My Account" on the side bar.
- Select "edit" link next to "Account Details."
- Type the following in the "Public RSA SSH Key:" field:
- Click the "Save!" button.
- Verify your success. You will see "ssh-rsa" followed by alpha numeric string in "Public SSH Key:" field of your Account Details.
- Each Fedora contributor has 2000000 KiB (approximately 1954 MiB) of quota-controlled space.
- If you run out of space you should: clean up stuff you don't need. If you cannot clean up anything then you should contact fedora infrastructure to raise your quota.
- To make a publicly viewable space, create a
- Fedora people is NOT to be used for development or creating repositories on. Repositories will need to be created elsewhere and uploaded via scp or rsync.
- DO NOT try to use sudo to install packages you "need." Unless you are in the Infrastructure group, and have gotten approval from sysadmin-main, extra packages are not to be installed on fedorapeople.
- Upload files using scp, sftp, or rsync.
To copy files from the command line, you can use scp
scp /path/to/file firstname.lastname@example.org:/home/fedora/your_username/public_html
- Once uploaded into the users public_html directory the files are available via http at: http://your_username.fedorapeople.org/.
- Give other users access to read/write/etc files by using extended acls. Read man pages for setfacl and getfacl for adding them to your dirs/files. This gives the user "your_usename" read and write access to
setfacl -m u:your_username:rw file
fedora people git hosting support
fedorapeople.org now has support for hosting git repositories including accessing them via the git:// protocol for anonymous downloads as well as providing the cgit web interface.
Here is a quick rundown of how to get started using git on fedorapeople.org. It assumes that you are already somewhat familiar with git. You might want to take a look at the Git quick reference.
~/public_git directory on fedorapeople.org
ssh email@example.com "mkdir ~/public_git; /sbin/restorecon -Rv ~/public_git"
Creating a new git repository in
As an example, here is one method to create an empty repository on your local system and upload it:
git init --bare repo.git scp -r repo.git/ firstname.lastname@example.org:~/public_git/
This creates a bare repository (i.e. a repository that has no working directory). It contains just the files that are part of the
.git directory of a non-bare git repository (the kind most users are accustomed to seeing).
Additionally if you wish your repository to show up in the cgit web interface, you must:
For any repositories you wish to appear there by default.
Uploading an existing repository to
If you have an existing repository you want to use on fedorapeople, you can do so easily:
git clone --bare /path/to/local/repo repo.git scp -r repo.git/ email@example.com:public_git/
The caveats from the previous section apply here as well.
Pushing to your repository
To push changes from a local repository:
cd /path/to/local/repo git remote add fedorapeople firstname.lastname@example.org:public_git/repo.git git push --mirror fedorapeople
This creates a mirror of your local repository. All of the branches and tags in the local repository will be pushed to the fedorapeople repository.
If you only want to push selected branches, amend the
git push example. For example, to push only your local master branch:
git push fedorapeople master
Cloning your repository
To clone your repository, use a command similar to:
git clone git://fedorapeople.org/~your_username/repo.git
It is also possible to clone your project via the http:// protocol. In order for this to work, you must arrange to have
git-update-server-info run whenever you update your repository. Typically, this is done with a post-update hook script. However, the user home directories on fedorapeople.org are mounted with the noexec option, which prevents the script from running. Instead, you may create a symbolic link to
git-update-server-info in the hooks directory of your repository:
ssh email@example.com cd ~/public_git/repo.git/hooks ln -svbf $(git --exec-path)/git-update-server-info post-update git update-server-info
You also need to create a link from ~/public_html/git to ~/public_git:
cd ~/public_html ln -svbf ../public_git git
You can clone your repository over http:// with a command similar to:
git clone http://your_username.fedorapeople.org/git/repo.git/
Browsing your project via cgit
You can see your project listed in cgit once the project list updates. This happens hourly.
If you want to give access to your repository to other users you can do this with ACLs.
setfacl -R -m u:<user>:rwX <repo.git> find <repo.git> -type d | xargs setfacl -R -m d:u:<user>:rwX
Enable per-repo upload-archive
If you want to allow your repository to be accessible via
git archive --remote , you will need to set set the following in your repostiory's config file:
[daemon] uploadarch = true