You are not logged in.
Pages: 1
Hi!
I would like to create a ftp repository for pacman..
is there any guide or hint how to configure it?
thanks
Offline
Let's get this out of the way first: FTP Must Die. Seriously, use http, you and anyone who uses your repo will be so much happier.
But if you insist... what you're asking is essentially how to set up a FTP server, to which the general answer is "install it and configure it" - more specifically, there are a number of ftp server packages in the Arch repos and/or the AUR, e.g. vsftpd, which even has its own wiki page.
The repo-specific bit is essentially the repo-add command, which you already have as part of the pacman package.
Offline
Ok.. So i will use http ![]()
Apache , nginx?
Any special settings? Like directory structure?
Offline
Apache , nginx?
Yes - or lighttpd, or any other http server. Which one do you prefer?
Any special settings? Like directory structure?
Not particularly - as per the advice above, read the relevant documentation.
Offline
On the top right in that grey bar is a button that reads "Wiki". Behind that button hides our super secret wiki. On the top left is an edit box that reads "search". You might want to try the query "repository". If the first article you find does not have what you need, on the top right of every article, there is a section with related links. it actually reads "Related articles", but don't let that have you stray from your path! A few hints on your search queries. You want to create a "repository" or maybe even many "repositories", you are a "user" of Arch and your repository will probably be "unofficial".
Offline
I have read our super special wiki but there isn't any guide how to setup a repo..
if you are so good to spot one let me know otherwise I don't need any ironic rtfm ![]()
Offline
Hehe, okay, since I spotted one, you are entitled to one free ironic rtfm (as delivered; we work fast, you don't even need to order; thank you for your purchase).
https://wiki.archlinux.org/index.php/Cu … repository
This post explains the rest:
You can just follow that wiki page en upload your pkg.tar.gz files and the $reponame.db.tar.gz file to your website of choice.
Offline
this is a local repo and already have one.. I need an online one ![]()
Offline
I'm not sure I understand. A repo is a place you keep the packages, so you simply want to host some files, right? Dropbox is enough. If you want to host it yourself, https://wiki.archlinux.org/index.php/Lighttpd is a good start (based on tomk's recommendation).
Why do you want a repo?
Offline
I need one for my job.. I have a lot of archlinux clients and some customers doesn't allow to use third party cloud services like dropbox.
I need to keep inside of this repo some customized packages.
What i would like to know was:
What to add in pacman.conf
How to structure the web directories (i.e. what does it mean $repo ?)
I know i can make trials but an official wiki was better!
Offline
Best of all - make trials, as you put it, then write the "official" wiki page yourself!
Offline
Eheheh ok i'll do it ![]()
Offline
I'll just add that since you already have a local repo, all you're missing is the http server.
pacman.conf is very straightforward, just read the man page - it even tells you what '$repo' means. ![]()
Offline
I'll just add that since you already have a local repo, all you're missing is the http server.
Pretty much this. Once you've decided on your http server, you can then decide how to structure the folders on it.
It's a shame about Dropbox, because it is super simple to use. However, you do have to pay $100 p/year if you want the "Public" folder (so you can structure it like a public repository, instead of sharing random links each time you want to share a file) and you'll need the dropbox-index package for people to view what's in there.
Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository
Offline
this is a local repo and already have one.. I need an online one
Well, it boils down to moving your local repository folder to a web server and point at it in the pacman.conf. The reason we don't have a single condensed tutorial for everything is the redundancy of redundancy.
It's a shame about Dropbox, because it is super simple to use. However, you do have to pay $100 p/year if you want the "Public" folder (so you can structure it like a public repository, instead of sharing random links each time you want to share a file) and you'll need the dropbox-index package for people to view what's in there.
The good software always has a problem of one kind or the other. In dropbox's case it's not a software problem, but politics and economy.
Last edited by Awebb (2015-02-11 14:21:40)
Offline
Pages: 1