This page covers the details on how to obtain and use your personal space on fedorapeople.org, a site where Fedora contributors can upload files to share with the world. It is perfect for uploading specfiles, SRPMs, patches, or personal Git repositories.
- 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 the 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. Private .ssh keys found during an audit will be deleted.
Accessing your fedorapeople.org space
- You need an active Fedora account
- You must be part of at least one group (other than the CLA group) in the Fedora account system. Often annotated as CLA+1
- You need to generate a ssh key (
ssh-keygen -t rsa).
- Upload the ssh key into your Fedora account. To upload, visit this link and select your key file using the Public RSA SSH key field. Oftentimes, your public key can be found in your home directory under
.ssh/id_rsa.pub. The ssh key will become activated an hour after it is uploaded.
- To connect, use the ssh key you uploaded into your Fedora account:
ssh -i ~/.ssh/id_rsa <your_username>@fedorapeople.org
- Each Fedora contributor has 2000000 KiB (approximately 1954 MiB) of quota-controlled space.
- If you run out of space, you should clean up files you don't need. If you cannot clean anything up, you should contact Fedora Infrastructure team to raise your quota.
- You need to change the permissions for your home directory to at least
711to make it viewable.
chmod 711 $HOME
- To make a publicly viewable space, create a
public_htmldirectory and set it's permissions to
- Fedora people is NOT to be used for development or repository creation. Repositories will need to be created elsewhere and uploaded via
- 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.org.
- Upload files using
To copy files from the command line, you can use
scp /path/to/file firstname.lastname@example.org:/home/fedora/your_username/public_html
- Once files are uploaded into the user's
public_htmldirectory, the files will become available at: https://your_username.fedorapeople.org/.
- Give other users access to read/write/etc files by using extended ACLs. Read man pages for
getfaclfor adding them to your dirs/files. This gives the user
your_usernameread and write access to
setfacl -m u:your_username:rw file
fedorapeople.org git hosting support
fedorapeople.org now has support for hosting git repositories. This includes access via the
git:// protocol for anonymous downloads as well as providing the cgit web interface.
Create a ~/public_git directory on fedorapeople.org
ssh email@example.com "mkdir ~/public_git; /sbin/restorecon -Rv ~/public_git"
Creating a new git repository in ~/public_git
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 run the following command for any repositories you wish to appear there by default:
Uploading an existing repository to ~/public_git
If you have an existing repository you want to use on fedorapeople.org, 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.org 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
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 repository's config file:
[daemon] uploadarch = true
fedorapeople.org servers are regularly scanned for viruses, including people's home directories, because of the nature of providing download of user-uploaded files on a Fedora domain name. As soon as a virus is reported by the scanners, they will be scanned again by another scanner to make sure they're actual viruses (and not just an overly active scanner). If the second opinion also reports the file as being a virus, the file will be moved to a non-public facing directory, and the owner will be notified. If the user has not yet responded after a week, the file will be deleted.