Search results

From MusicBrainz Wiki
Jump to navigationJump to search

Page title matches

  • #REDIRECT [[History:Development/Sandbox]]
    41 bytes (4 words) - 18:23, 5 February 2020
  • =MusicBrainz Server Coding Style= ...code> to load the class whose name it is given. The <code>/lib/MusicBrainz/Server/Model/</code> directory is not used for this, oddly enough.
    8 KB (1,382 words) - 23:32, 28 March 2017
  • #REDIRECT [[History:Development/Search server setup]]
    53 bytes (6 words) - 15:14, 10 September 2020
  • ...nderstands the following environment variables, these may be useful during development: Set this to "1" when you want to run the server against the test database, this is typically used to debug selenium tests:
    675 bytes (100 words) - 08:38, 2 March 2012
  • #REDIRECT [[Development/Search server setup]]
    45 bytes (5 words) - 18:15, 31 January 2012

Page text matches

  • == MusicBrainz server == # [[Server Setup|Server Setup]]
    1 KB (150 words) - 08:35, 17 July 2023
  • ...nderstands the following environment variables, these may be useful during development: Set this to "1" when you want to run the server against the test database, this is typically used to debug selenium tests:
    675 bytes (100 words) - 08:38, 2 March 2012
  • #REDIRECT [[Development/Server Coding Style]]
    45 bytes (5 words) - 02:05, 9 September 2012
  • #REDIRECT [[Development/Server Coding Style]]
    45 bytes (5 words) - 19:46, 9 September 2012
  • #REDIRECT [[History:Development/Search server setup]]
    53 bytes (6 words) - 15:14, 10 September 2020
  • ...ade up of, and works with, several different components: the [[MusicBrainz Server]], [[MusicBrainz Database]], [[XML Web Service|web service]] (and related [ Our [[Timeline|development timeline]] records major releases and developer summits.
    2 KB (303 words) - 16:32, 20 May 2023
  • To create debian packages for, and to support, a [[MusicBrainz]] server. * musicbrainz-server (web stuff)
    941 bytes (129 words) - 08:41, 15 March 2009
  • ...ou probably want to use that server, or your own development server during development. When NGS has been released you should replace this with 'musicbrainz.org'
    3 KB (444 words) - 12:21, 12 November 2011
  • <small>[[Development]] > Bug Tracker</small> ...the community to track bugs and development progress on the [[MusicBrainz Server]] source code.
    2 KB (310 words) - 16:04, 28 October 2020
  • Some of the more complete translations are available on the only server at https://critiquebrainz.org/. == Development ==
    3 KB (354 words) - 18:34, 12 December 2023
  • See also [[Development]]. : Our C/C++ development library geared towards developers who wish to add cover art capabilities to
    4 KB (539 words) - 14:06, 28 October 2023
  • * Develop MusicBrainz Server itself. ...it only if you cannot use MusicBrainz Docker for some reason (disk space, development, …).
    3 KB (498 words) - 19:58, 28 March 2023
  • ==MusicBrainz Development== The community is actively [[Development|developing]] MusicBrainz, and offers a number of different [[Products|produ
    2 KB (357 words) - 20:10, 29 February 2024
  • == Development == A POT file is provided with all the strings used in the server. They are in English.
    2 KB (253 words) - 18:35, 12 December 2023
  • <small>[[Development]] > MusicBrainz Projects </small> ...ing mod_perl with the Mason web framework. [[Image:Attention.png]] Further development on this version of MusicBrainz has been stopped.
    4 KB (616 words) - 15:23, 24 June 2013
  • ...ion.png]] '''This service is now deprecated and should NOT be used for new development!''' ...ia the standard HTTP protocol. This Web Service should be used for all new development.
    2 KB (297 words) - 03:42, 19 September 2012
  • ...led "CDDB.com" could be used to access the information of Audio CDs. This server accepted new submissions of Audio CD information. At that stage the index ...me popular and useful. Things changed dramatically when the open CDDB.com server was bought by a company that wanted to make money from the contributions th
    4 KB (599 words) - 20:14, 10 July 2020
  • <small>[[Development]] > Timeline</small> == Currently under development ==
    6 KB (933 words) - 11:46, 26 May 2015
  • Development on the [[MusicBrainz Server]] source code is coordinated using [http://git-scm.com/ Git]. To create a local copy of the [[MusicBrainz Server]] source code, clone the repository using:
    6 KB (1,014 words) - 07:41, 3 August 2019
  • ...usicBrainz Client Library (libmusicbrainz), also known as mb_client, is a development library geared towards developers who wish to add MusicBrainz lookup capabi ...the [ftp://ftp.musicbrainz.org/pub/musicbrainz/historical/ MusicBrainz FTP Server].''
    2 KB (232 words) - 11:26, 28 October 2023
  • (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
    3 KB (431 words) - 10:18, 5 March 2019
  • (see also: [[Development/Summer of Code/Getting started|Getting started with GSoC]]) === Use Solr search server===
    4 KB (687 words) - 13:21, 5 April 2024
  • ...available, [[Style|style guidelines]] are changed or are added to, or new server features are implemented. ...cated to the Open Source software development model, and thus the [[Server|server]] and client libraries are available under the [https://www.gnu.org/copylef
    5 KB (780 words) - 05:19, 3 March 2023
  • (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
    5 KB (899 words) - 15:12, 3 February 2020
  • The list of open tasks is kept on our [[Bug Tracker]], and on [[MusicBrainz Development]], and they change quite frequently. === MusicBrainz Server Developer ===
    3 KB (406 words) - 16:20, 26 August 2016
  • (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
    3 KB (574 words) - 16:27, 18 February 2017
  • <small>[[Development]] > Subversion Repository </small> The [[MusicBrainz Server]] is currently the only project that has made the transition; the source co
    2 KB (307 words) - 11:46, 26 May 2015
  • ...ith the feature. It's now merged into master, and will be part of the next server release. ...nt, as it won't be possible to test these features against a live database server.
    3 KB (582 words) - 14:02, 7 March 2012
  • ...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 * Install the server on your computer or use the Vagrant setup scripts to build a virtual machin
    4 KB (595 words) - 16:36, 16 March 2016
  • === Development === ...in May 2011 after more than five years of planning and two years of active development!
    11 KB (1,575 words) - 20:20, 12 April 2012
  • (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
    6 KB (1,030 words) - 20:25, 13 March 2017
  • (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
    7 KB (1,105 words) - 10:16, 17 February 2021
  • ...Schema]] (NGS). NGS would prove to be our number one task in 2010, with no server releases happening at all because of our focus on NGS. ...m in the process of writing NGS. From Nov 2009 to Feb 2010 the MusicBrainz Server codebase went from ~224,000 lines of code down to ~72,000 (the lowest since
    10 KB (1,427 words) - 03:18, 11 January 2012
  • This page is intended for translators of [[MusicBrainz Server]] and [[MusicBrainz Database]]’s semi-static content, and people interest * MusicBrainz Server/Database translation: Use the [https://community.metabrainz.org/tags/c/musi
    12 KB (1,709 words) - 19:29, 12 December 2023
  • (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
    8 KB (1,324 words) - 14:52, 23 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
    4 KB (745 words) - 14:29, 29 January 2018
  • ...pecific collaboration artist credit is credited to (similar to the current server's collaboration artist pages). ...rather see proposals that extend the Picard tagger and help along with its development.
    7 KB (1,187 words) - 19:46, 31 January 2012
  • # and finally builds searchable documents and sends these to the Solr search server. === Searching from MusicBrainz mirror without local Solr server ===
    8 KB (1,143 words) - 08:38, 21 January 2021
  • * "Artist was last updated X days ago" display in the server. ...the label associated with the release to be updated. However, our database server buckled under the load to constantly update all of this information so we w
    6 KB (916 words) - 21:08, 16 April 2009
  • ...to 2009 before seeing benefit from this work. Consequently we had only one server update in all of 2008, but we're expecting to have about 3 major releases t | Development
    9 KB (1,236 words) - 20:42, 8 January 2012
  • ...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
  • ...meetings open to interested parties, and open IRC channels. The client and server software will remain free and accessible under generally accepted open lice
    3 KB (437 words) - 19:39, 9 September 2012
  • =MusicBrainz Server Coding Style= ...code> to load the class whose name it is given. The <code>/lib/MusicBrainz/Server/Model/</code> directory is not used for this, oddly enough.
    8 KB (1,382 words) - 23:32, 28 March 2017
  • ...equested from the web service with ''inc='' calls (except for those that [[Development/XML_Web_Service/Version_2#Subqueries|need a subquery]]): aliases, annotatio gpg: requesting key C777580F from hkp server keys.gnupg.net
    5 KB (761 words) - 13:25, 5 May 2023
  • (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
    18 KB (2,856 words) - 16:10, 4 March 2024
  • (see also: [[Development/Summer of Code/Getting started|Getting started with GSoC]]) MusicBrainz Server can send emails to users in different occasions: email verification, edit n
    6 KB (852 words) - 12:03, 27 February 2024
  • This page attempts to outline the development team's priorities in broad strokes -- this priority list should serve as a # Server-side versioning for new extractor and storage of detailed lowlevel files
    5 KB (731 words) - 17:07, 18 January 2024
  • ...urther improvements and ironing out the kinks from that major release. Our development team pushed out updates weekly for a number of months, before falling back ...ed by Robert Kaye (ruaok). Ian broke language barriers and took on [[mbdoc:Server Internationalisation|internationalisation support]]. Ian was mentored by Ni
    18 KB (2,597 words) - 16:24, 26 December 2013
  • ...annot currently deploy only the webservice. We also have a separate Search Server application that searches over Lucene indexes built from the database, this ...erscripts (on MB, on geordi, on other sites?), geordi patches, musicbrainz-server patches, whatever's appropriate
    8 KB (1,403 words) - 09:53, 24 August 2013
  • ...discourage you from checking out some of these projects! The [[MusicBrainz Server]] is written in readable, well-structured Perl. If you're comfortable in e. ...ng interface. You also need to figure out how to modify our web service ([[Development/XML Web Service/Version 2]]) to indicate which tags are genres. (The web se
    6 KB (1,012 words) - 22:16, 9 February 2017
  • ...many kinds of contributions that make free and open source software (FOSS) development possible. Students must complete tasks, one at a time. It is sponsored and |Software Engineer at MetaBrainz, Co-Maintainer of MusicBrainz Server.
    7 KB (901 words) - 18:28, 15 March 2018
  • <span style="font-size:smaller">(see also: [[Development/Summer_of_Code/Getting_started|Getting started with GSoC]])</span> ...pressJS is required to find and replace the relevant components in the web server.
    9 KB (1,504 words) - 14:23, 25 March 2020
  • (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
    15 KB (2,483 words) - 12:55, 11 April 2022
  • <span style="font-size:smaller">(see also: [[Development/Summer_of_Code/Getting_started|Getting started with GSoC]])</span> * Creating the web server routes and add the new entity type to the entity saving mechanism with test
    8 KB (1,206 words) - 13:55, 25 May 2021
  • ...discourage you from checking out some of these projects! The [[MusicBrainz Server]] is written in readable, well-structured Perl, using the web application f [[Server Internationalisation]] would be much easier for translators if it could be
    12 KB (1,901 words) - 17:21, 28 April 2020
  • ...s. The URIs are just names, they should not be used to query data from the server. But they are in a permanent format which will always be valid and can easi ...le transformation. It can be used to request data from the [[MusicBrainz]] server via the API. URLs may change over time, the URIs will not.
    16 KB (2,378 words) - 20:09, 10 July 2020
  • ...uthentication of the user and authorization to perform actions using the [[Development/XML_Web_Service/Version_2|web service]] on their behalf without getting the ...plications that can keep secrets. Typically web applications, running on a server.
    14 KB (2,217 words) - 12:14, 24 February 2024
  • * [[MusicBrainz_Server/Internationalization|MusicBrainz Server and data]] [[Category:Development]] [[Category:Internationalization]]
    7 KB (937 words) - 20:28, 20 December 2023
  • <span style="font-size:smaller">(see also: [[Development/Summer_of_Code/Getting_started|Getting started with GSoC]])</span> ** privileged editors can trigger a reindex of the search server
    5 KB (815 words) - 21:21, 29 March 2023
  • ...o release new versions of the server software every two weeks and our core development team was focused on improving the site based on bug reports and feature req ...on fire. With the resources and bandwidth we have available right now, our server farm is decently loaded and still able to handle occasional traffic spikes.
    20 KB (3,043 words) - 12:46, 25 July 2014
  • ...lease focus on translating for Picard 3.x, as this is the current focus on development. The translations for identical strings will propagate to the translations ...ts are taken from the MusicBrainz Server project, please see [[MusicBrainz Server/Internationalization]] for details. Country names are used for preferred co
    24 KB (3,671 words) - 07:23, 18 December 2023
  • *Running MusicBrainz Server on Windows ([[User:YvanZo|yvanzo]] & [[User:Aerozol|aerozol]]) *Running/writing Selenium tests for MusicBrainz Server/Docker ([[User:Bitmap|bitmap]], reosarevok, yvanzo)
    7 KB (1,038 words) - 13:15, 5 October 2023
  • ...ng interface. You also need to figure out how to modify our web service ([[Development/XML Web Service/Version 2]]) to indicate which tags are genres. (The web se ...he features mentioned above and/or some of your own ideas. The musicbrainz-server codebase is written in Perl, and the current artist pages use Template Tool
    6 KB (956 words) - 16:33, 16 March 2016
  • (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
    20 KB (3,240 words) - 17:34, 1 April 2023
  • ...nd at <code>mb-solr</code> build time (in build logs), and at run time (in server logs) From [[Development/Search Architecture]], our repository [https://github.com/metabrainz/mb-sol
    9 KB (1,179 words) - 19:23, 11 January 2024
  • *Development led by Ian *Development led by Ollie
    10 KB (1,588 words) - 19:19, 1 June 2014
  • <span style="font-size:smaller">(see also: [[Development/Summer_of_Code/Getting_started|Getting started with GSoC]])</span> ** privileged editors can trigger a reindex of the search server
    9 KB (1,486 words) - 12:59, 30 March 2022