Finally, fucking finally, after twenty fucking trillion tries, a huge ass import is going steady and fast.

I'm literally, out loud, encouraging the import process 😅

"Yesyesyes keeeep it going!"
"You can do this!!"
"You're doing very well!"

I feel like a fucking retard but I'm so happy its finally starting to work 😅

I feel ya. I'm writing an import step for articles in the invoicing system that has to run at least daily and it's so fun every time I can shave some time off of it!

@epse That haha. Although in my case its 6+ billion records so 😅

@linuxxx that will mercilessly show even the smallest inefficiency!

@epse Yeah but it's a docker container and my docker skills aren't as good 😅

@linuxxx docker is an interesting beast to tame. Best of luck

@epse

Never had luck taming docker.
Allways I manage to fuck it up one way or another.

Even if someone once set it all up for me and made me simple note:
"use command docker --log <hash> to see output and to interact <this command> and quit using ^p^q"
I managed to brick app in docker within 2 weeks and to this day - no idea how and why.

@linuxxx - I have cheered before on success. Like hands up in a Y with fists and verbal noises. Accidentally scared the wife but you are not alone.

@DubbaThony I usually wrote logs to a file and synced to the host machine. I just tell them to check the logs on the host or ftp them if they need a local copy from the server. It's way easier imo.

@kavinci sometimes I needed interactive mode, maybe that screwed around.. I have no idea, after initial failures I just started avoid docker or push it to other people "if you really want docker, im not touching it, and not becouse of not wanting to help, rather im soft guarantee that i will brick it on accident" kind of way.

@DubbaThony lol, fair enough. I usually handled the interactive portion. Docker for me has both been a huge pain and a huge help all in one.