Search results

From MusicBrainz Wiki
Jump to navigationJump to search
  • ...to work on AcousticBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some * Install the server on your computer or use the Vagrant setup scripts to build a virtual machin
    6 KB (936 words) - 21:35, 21 February 2017
  • ; [[Development/Summer of Code/2024|2024]] [[Development/Summer of Code/2023|'''2023''']]
    10 KB (944 words) - 13:18, 5 April 2024
  • (see also: [[Development/Summer_of_Code/Getting_started|GSoC - Getting started]]) ...to work on AcousticBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some
    10 KB (1,594 words) - 10:19, 25 March 2019
  • ; [[MusicBrainz Server]] : The MusicBrainz Server is the web frontend to the [[MusicBrainz Database]], and is accessible at h
    3 KB (446 words) - 14:29, 5 March 2021
  • (see also: [[Development/Summer_of_Code/Getting_started|Getting started with GSoC]]) ...nt to work on ListenBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some
    6 KB (922 words) - 15:41, 28 February 2020
  • <span style="font-size:smaller">(see also: [[Development/Summer_of_Code/Getting_started|Getting started with GSoC]])</span> We’re currently in the process of switching to using Node.js for all server side code. As part of this, our schema has been redesigned, and the current
    3 KB (492 words) - 21:56, 14 March 2017
  • <span style="font-size:smaller">(see also: [[Development/Summer_of_Code/Getting_started|Getting started with GSoC]])</span> We’re currently in the process of switching to using Node.js for all server side code. As part of this, our schema has been redesigned, and the current
    3 KB (492 words) - 04:34, 17 January 2018
  • (see also: [[Development/Summer_of_Code/Getting_started|Getting started with GSoC]]) ...nt to work on ListenBrainz you should show that you are able to set up the server software and understand how some of the infrastructure works. Here are some
    6 KB (950 words) - 17:07, 29 March 2021
  • musicbrainz-server doesn't currently run with any translation, although we have some partial s [[Server Internationalisation]] links to relevant transifex, language-specific trans
    7 KB (1,124 words) - 09:53, 24 August 2013
  • * [http://musicbottle.mbsandbox.org/ Code running on the MusicBrainz sandbox server.] (Not guaranteed to be running.) ...ing into. We will most likely aim for getting the code running on an nginx server.
    7 KB (1,032 words) - 14:46, 1 May 2014
  • ...of the computing power than the code it replaced. In 2009 we only had one server release that brought us Release Groups and ISRC support - we had planned to ...g and we started the process of moving from Subversion to Git for the main server codebase. And Kuno Woudt quit his job and prepared to come to work for the
    10 KB (1,390 words) - 07:49, 17 November 2013
  • NGS is coming, so a rewrite is in order to keep up with MB development. This wiki page collects information, plans, and ideas for this project. ...ce on the [http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-devel development mailing list]
    4 KB (547 words) - 00:03, 16 January 2013
  • # MusicBrainz server development over the summer. Perl, python, Template::Toolkit # Moving to mod_perl 2, but I suspect that's covered by "server development", above - [[User:DaveEvans|DaveEvans]]
    5 KB (701 words) - 20:30, 26 May 2015
  • MusicBrainz server log analysis is one of the Google Summer of Code projects for the summer of * The [http://plaintextgsoc.wordpress.com/ development blog] of the Summer of Code project
    4 KB (595 words) - 13:37, 1 June 2012
  • :Have you looked at the ideas pages for [[Development/Summer of Code/2024#Projects|each project]]? At this point, you should be familiar with basic open source development tools and workflows, and your [http://lmgtfy.com/?q=google-fu Google-fu] sh
    7 KB (1,210 words) - 13:19, 5 April 2024
  • ...xed Search Syntax|syntax documentation]]) and what data is returned (see [[Development/XML Web Service/Version 2/Search]]). ...3722]] - Potentially useful for anyone looking into doing this: The search server supports searching across all entities, but we have no interface which supp
    8 KB (1,280 words) - 12:56, 23 March 2015
  • NOTE: the /ws/js webservice is considered to be part of the musicbrainz server code. it isn't version and may change at any time, please do not rely on i [[Category:Development]]
    3 KB (359 words) - 09:52, 24 August 2013
  • - 406 if the server is unable to generate a response suitable to the Accept header. ...ch request methods are valid for each resource. On an OPTIONS request, the server will do no processing, other than returning an empty response with the 'All
    13 KB (1,790 words) - 12:50, 23 March 2024
  • ...ck space MusicBrainz today has 6 computers in active service and one spare server to cover hardware failures. ...calable services in anticipation of upcoming growth. During this sponsored development time a new Lucene full text search, a new XML Web Service and the MusicDNS/
    22 KB (3,222 words) - 18:37, 18 December 2011
  • <span style="font-size:smaller">(see also: [[Development/Summer_of_Code/Getting_started|Getting started with GSoC]])</span> You will be expected to use test driven development, as well as prepare a documentation that will be available for the public.
    7 KB (1,133 words) - 11:51, 20 March 2019
View ( | ) (20 | 50 | 100 | 250 | 500)