Okay I'll get started with the MB application part.
2019-12-15 34910, 2019
sarthak_jain
I need to create an account? Right?
2019-12-15 34947, 2019
pristine__
Nice. So we are generally away on weekends, but if you want to ping anyone on weekends just leave a message, we usually read backlogs, so your queries will be answered definitely.
2019-12-15 34949, 2019
pristine__
Yee
2019-12-15 34959, 2019
pristine__
Visit the application page. There is a link :)
2019-12-15 34900, 2019
pristine__
sarthak_jain: you don't need to initialize spotify ids and Last fm ids unless you are going for development in LB-server. After updating config.py with Musicbrainz ids, you can directly go to "initialize listenbrainz containers"
2019-12-15 34925, 2019
sarthak_jain
Oh.. you saved me. Was about to get to that
2019-12-15 34928, 2019
sarthak_jain
:p
2019-12-15 34948, 2019
pristine__
We are setting up lb-server before labs because labs uses server's network.
Version in "./docker/docker-compose.yml" is unsupported.
2019-12-15 34910, 2019
sarthak_jain
ERROR: Version in "./docker/docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use
ERROR: yaml.parser.ParserError: while parsing a block mapping in "./docker/docker-compose.yml", line 2, column 1expected <block end>, but found '-' in "./docker/docker-compose.yml", line 125, column 1
2019-12-15 34934, 2019
pristine__
Check for the syntax
2019-12-15 34922, 2019
pristine__
Did you close the double quotes?
2019-12-15 34915, 2019
pristine__
Since I am not at your end, I cannot see wht you have written. In case of errors, the first step is to google the error since you know what you have written :)
2019-12-15 34940, 2019
sarthak_jain
I dint write. I copy pasted the content of the file on the git
2019-12-15 34946, 2019
pristine__
Okay. Go to listenbrainz-server/docker/docker-compose.yml file in your local machine
2019-12-15 34935, 2019
n1tr0maverick has quit
2019-12-15 34906, 2019
pristine__
On line you will see version:"3.4"
2019-12-15 34922, 2019
sarthak_jain
Yes
2019-12-15 34924, 2019
pristine__
Change it to 3.7 and save
2019-12-15 34925, 2019
sarthak_jain
I do see
2019-12-15 34934, 2019
pristine__
Keep the quotes intact
2019-12-15 34955, 2019
pristine__
Then run ./develop.sh
2019-12-15 34914, 2019
pristine__
And make sure that you are inside listenbrainz-server directory while running the commands
2019-12-15 34945, 2019
sarthak_jain
Yes
2019-12-15 34952, 2019
sarthak_jain
when i run ./develop.sh
2019-12-15 34954, 2019
sarthak_jain
version: "3.4"# IMPORTANT NOTE: Volume paths mounted on containers are relative to the# directory that this file is in (`docker/`) and so probably need to start with# `../` to refer to a directory in the main code checkoutvolumes: postgres: redis: influxdb: rabbitmq:services: db: image: postgres:9.5.3 volumes: -
Define and run multi-container applications with Docker.Usage: docker-compose [-f <arg>...] [options] [COMMAND] [ARGS...] docker-compose -h|--helpOptions: -f, --file FILE Specify an alternate compose file (default: docker-compose.yml) -p, --project-name NAME Specify an alternate project name (default: directory name) --verbose
2019-12-15 34928, 2019
sarthak_jain
Show more output -v, --version Print version and exit -H, --host HOST Daemon socket to connect to --tls Use TLS; implied by --tlsverify --tlscacert CA_PATH Trust certs signed only by this CA --tlscert CLIENT_CERT_PATH Path to TLS certificate file --tlskey TLS_KEY_PATH Path to TLS
2019-12-15 34929, 2019
sarthak_jain
key file --tlsverify Use TLS and verify the remote --skip-hostname-check Don't check the daemon's hostname against the name specified in the client certificate (for example if your docker host is an IP address)
