#1722 information about moving 389 to fedorahosted
Closed: Fixed None Opened 14 years ago by rmeggins.

We currently host our port389.org wiki and file server. Our servers are nearing EOL support, and they are migrating the hosting center, so we are considering moving to fedorahosted.org. We need the following:
1) Need to have port389.org - can we have a "virtual" hostname? I'd rather not have to have redirects, that is, every time someone goes to http://port389.org/someurl they see http://389.fedorahosted.org in their web browser
2) We currently have a download space for source tarballs, binaries for other platforms, etc. - would there be a download space available for a hosted project?
3) Our port389.org wiki is in MediaWiki 1.6 format - how big a migration will it be to use the fedorahosted.org wiki format?


Hi,

I think all your points can be attended, however I will have point #1 to be fully answered by someone more in touch with the way the infrastructure works. From what I can see it is possible, but I don't know if there are any restrictions.
Point #2 can be accomplished using a third party plugin[1] to our trac instance which (fortunately) is compatible with trac 0.10 (which we have in fh.o)
Point #3 I am sure there are several conversion plugins (here is one[2]) floating around, so I believe there wouldn't be much of a problem.

Hope that answers some of your questions

[1] http://trac-hacks.org/wiki/DownloadsPlugin
[2] http://trac.edgewall.org/attachment/wiki/TracWiki/mediawiki2trac.py

I don't see this as fixed :(

port389.org still goes to an old MW instance, and is rewritten as directory.fedoraproject.org.

Rich -

Is there still interest in this? The MW to trac migration might be tricky, never used that python script.

#2 is trivial with how we currently do things, the difficulty with 389 would be that there's a 1:1 mapping of release areas (to store tarballs, whatnot) per git repo, which you have a good number of, and I'm not sure if you want one cohesive release area or several.

I'm thinking that #1 could be accomplished, but it would be a oneoff, which we like to avoid, but if it's a requirement, we can do it.

I'm not sure we offer this in fedorahosted. We considered it at one time but the costs of doing it are too high. We would have to get an IP address for everyone who requests their domain be something other than fedorahosted.org? It just doesn't work :-/

We're going to use a different hosting environment for 389. You can consider this issue closed.

Login to comment on this ticket.

Metadata