Difference between revisions of "Haskell.org domain"

From HaskellWiki
Jump to: navigation, search
(update to point to new resources)
 
(25 intermediate revisions by 8 users not shown)
Line 2: Line 2:
   
 
== Overview ==
 
== Overview ==
  +
The names in the '''haskell.org domain''' point to a set of machines. The bulk of those machines are now cataloged on the [https://phabricator.haskell.org/w/infrastructure/ Haskell Phabricator Wiki]
   
The '''haskell.org domain''' includes these names:
 
  +
Certain machines had been made available for community hosting in the past, and many still exist on [http://community.haskell.org community.haskell.org]. However, given the rise of new options for hosting, we are discouraging the use of these servers, and would like to help those now currently using them to find a way to host their content elsewhere. See the February 2015 blog post [https://blog.haskell.org/post/the_future_of_community_haskell_org/ The Future of Community.Haskell.Org] for more.
   
* [[haskell.org]], [http://www.haskell.org/ www.haskell.org], [http://bugs.haskell.org/ bugs.haskell.org], at Yale university. <br>This machine runs the web server, wiki, and mailing lists.<br>''MRTG'': [http://www.haskell.org/mrtg/localhost_00-c0-a8-7b-85-3c.html All network traffic].
 
  +
== Policy on adding new subdomains ==
   
* [http://darcs.haskell.org/ darcs.haskell.org], [http://hackage.haskell.org/ hackage.haskell.org], [http://cvs.haskell.org/ cvs.haskell.org], [http://haskell.galois.com/ haskell.galois.com], run by Galois. <br>This machine serves the central darcs repositories for the projects hosted at darcs.haskell.org, the darcsweb service, and it also runs the various Trac instances (eg. http://hackage.haskell.org/trac/ghc).<br>''MRTG'': [http://darcs.haskell.org/mrtg/localhost_00-11-2f-2e-4f-7c.html All network traffic], [http://darcs.haskell.org/mrtg/external-bandwidth.html External network bandwidth], [http://darcs.haskell.org/mrtg/freedisk.html Free disk space], [http://darcs.haskell.org/mrtg/system-load.html System load], [http://darcs.haskell.org/mrtg/memory.html Free memory], [http://darcs.haskell.org/mrtg/swap.html Free swap], [http://darcs.haskell.org/mrtg/daily.html All of the daily graphs].<br>''Analog'': [http://darcs.haskell.org/analog/cvs_darcs/cvs.html cvs/darcs], [http://darcs.haskell.org/analog/hackage/hackage.html hackage].
 
  +
We limit the addition of new subdomains to haskell.org to minimise unnecessary proliferation of subdomains and to try to keep the haskell.org domain reasonably well organised, while still helping people do useful things with it.
   
* [http://community.haskell.org/ community.haskell.org], [http://code.haskell.org/ code.haskell.org], [http://trac.haskell.org/ trac.haskell.org], [http://rt.haskell.org/ rt.haskell.org] <br>for hosting anyone's Haskell projects. See [http://www.haskell.org/pipermail/haskell/2007-June/019592.html this message].
 
  +
The policy has been that new subdomains are to be used for services rather than content.
   
== Relation between the services ==
 
  +
So for example a Haskell graphics related website would normally go at <nowiki>http://www.haskell.org/graphics</nowiki>, rather than <nowiki>http://graphics.haskell.org</nowiki>.
   
''I'm wondering what the relationship is (if any) between code.haskell.org and darcs.haskell.org.''
 
  +
In contrast a service like hackage does merit its own subdomain.
   
darcs.haskell.org hosts ghc, the core libs and many others.
 
  +
In either case, adding either new services or subsites is fairly rare and such requests will be considered on their own merits, on a case-by-case basis.
The server is maintained by Galois.
 
Because it hosts the most central bits of the haskell platform,
 
security is fairly tight and getting an account there is hard.
 
There are very few community members with root privileges.
 
 
community.haskell.org was created precisely to provide hosting to the wider community.
 
It is hosted commercially, paid for by haskell.org's Google Summer of Code funds.
 
We have several community admins with root privileges.
 
 
''Should my projects be hosted at darcs or code?''
 
 
code.haskell.org
 
 
It's easy to get an account there via the web submission system: http://community.haskell.org/admin/
 
 
''Is one more blessed/preferred over the other for community projects?''
 
 
Yes, code.haskell.org is preferred.
 
 
''If my project is currently on darcs, should I migrate to code?''
 
 
You can if you like, there is no need to do so however.
 
Accounts on darcs.haskell.org are not going to be revoked as far as I know.
 
The community server is an addition, not a replacement.
 
 
''If I have an account on darcs, will it work on code, or do I need to get a new account on code?''
 
 
They are totally separate systems.
 
 
== See also ==
 
 
http://www.haskell.org/pipermail/haskell-cafe/2008-January/038759.html
 

Latest revision as of 16:44, 28 May 2015


Overview

The names in the haskell.org domain point to a set of machines. The bulk of those machines are now cataloged on the Haskell Phabricator Wiki

Certain machines had been made available for community hosting in the past, and many still exist on community.haskell.org. However, given the rise of new options for hosting, we are discouraging the use of these servers, and would like to help those now currently using them to find a way to host their content elsewhere. See the February 2015 blog post The Future of Community.Haskell.Org for more.

Policy on adding new subdomains

We limit the addition of new subdomains to haskell.org to minimise unnecessary proliferation of subdomains and to try to keep the haskell.org domain reasonably well organised, while still helping people do useful things with it.

The policy has been that new subdomains are to be used for services rather than content.

So for example a Haskell graphics related website would normally go at http://www.haskell.org/graphics, rather than http://graphics.haskell.org.

In contrast a service like hackage does merit its own subdomain.

In either case, adding either new services or subsites is fairly rare and such requests will be considered on their own merits, on a case-by-case basis.