shivam-kapila: i think we need to mention why we didn't actually do the redesign in the work product
or just not mention the redesign at all because we didn't do it
i don't think putting in screenshots of a design we didn't do in the end is a good idea.
i think it's probably a good idea to not structure this doc in terms of phases, because there's really not much to say about phase 2.
Maybe structure it in terms of "Things that I changed", "Things that I'm working on currently"
shivam-kapila
iliekcomputers: thanks
I will update and ping you
Gore has quit
Gore joined the channel
antlarr has quit
iliekcomputers: One question
rdswift has quit
rdswift joined the channel
hugo___ has quit
SomalRudra has quit
mruszczyk has quit
revi has quit
alastairp has quit
zas has quit
jmp_music_ has quit
iliekcomputers has quit
loujine has quit
prabal has quit
zas joined the channel
SomalRudra joined the channel
hugo___ joined the channel
alastairp joined the channel
iliekcomputers joined the channel
revi joined the channel
prabal joined the channel
Leftmost has quit
Leftmost joined the channel
jmp_music_ joined the channel
loujine joined the channel
antlarr joined the channel
antlarr has quit
adhawkins
Hi all, trying to set up the musicbrainz server as a docker container using the official instructions. Seems to be basically working, but got a couple of issues:
prabal has quit
1. (not a deal-breaker) the images etc on the web pages seem to be referenced using 'localhost' style URLs. Presumably somewhere I have to specify the host name of the machine the container is running on so that I can access it from elsewhere on the network. How do I do this?
2. When trying to set up replication, I'm getting this in slave.log when I run the replication script: https://paste.debian.net/1161824/
It's a VM so if need be I could revert and start again.
yvanzo
adhawkins: for 2. I found that instructions are misleading, will fix that
diru110026 joined the channel
adhawkins
Ah, that probably won't have helped. Let me know if there's anything you want me to try. Happy to start again from scratch to 'debug' the instructions if need be.#
yvanzo
Since your local website is not currently in use, just stop it for initial replication.
sudo docker-compose stop musicbrainz
Then use "run" rather than "exec" for replication.
So will it 'just work' when I set up the automatic replication with the web server running?
yvanzo
So it is currently downloading hourly replication packets that have been created after the database dump you downloaded, it should take some minutes.
adhawkins
Yes, it's up to yesterday at 9am, so about 30 or so to process.
yvanzo
At best it probably takes 1 minute per hour in average, that is about 40 minutes in your case.
adhawkins
Yeah, it's about a minute per packet on this machine.
Ok, so once this finishes and I set up cron, would you expect it to 'just work'?
supersandro2000 joined the channel
yvanzo: The variable I set to setup a custom crontab, does that point to the file, or just the directory it's in?
I'll assume it's the path and file name, will see what happens.
In the container, how can I verify that it's using the correct one? Somewhere in /etc/cron.d?
ephemer0l has quit
shivam-kapila
reosarevok: can you take a look before I publish the blog
v6lur_ joined the channel
v6lur__ joined the channel
v6lur has quit
adhawkins
Ok, replication complete. Added the cron job. Any way within the container I can verify that it's set up using my custom crontab yvanzo?
v6lur_ has quit
yvanzo
Is the previous container stopped? (docker ps)
adhawkins
Yes, I stopped it, then used docker-compose up -d to restart everything
crontab -l is showing the correct crontab I think.
BrainzGit
[listenbrainz-server] vansika opened pull request #1063 (master…pydantic-model-dataframes): Pydantic model for data returned from spark (create_dataframes.py) https://github.com/metabrainz/listenbrainz-serv...
yvanzo
adhawkins: yes, it is
adhawkins
Perfect, just set a temporary time of 50 minutes pas the hour to make sure it's working.
Yep, it ran and said no packet was available. Will set it to the correct time and monitor.
yvanzo
If you see any difference between your cron file on your host and the file /crons.conf on the container, stop it and recreate it.
adhawkins
Yeah, just noticed that you have to explicitly down and up rather than just doing an 'up' and expecting docker-compose to rebuild (if you just change the crontab)
yvanzo
sudo docker-compose exec musicbrainz cat /crons.conf # to see the cron file in the container, doesn't always match `crontab -l` which is the only true.
adhawkins
All the style sheets etc seem to be loaded when I view the web page now too.