Honest Marie

I had not realized there was a console/debugger through Docker... I am rather unfamiliar with Docker, please forgive me D: Here are the logs from the Docker console. From connecting...

Yeah I had thought you meant for me to use Visual Studio Code to launch the debugger, so that's what I was doing. Here are more logs: Initial connection: ```2024-10-30...

Using the terminal provided within Docker (not the log console, the terminal. And it's Windows Powershell by the way, will provide a screenshot below), here is what I was returned...

> You do need to run the commands in the `pretendo-docker` directory with the `compose.yml` file - otherwise, Docker Compose can't know which containers you're talking about. I'm pretty sure...

That wasn't a good help. ;-; I sincerely apologize for that. I moved it into the ```pretendo-docker``` folder. Here is what the command ```docker compose ps --all``` returned with: ```...

I hadn't changed anything when I cloned your repo, so I'm unsure why it would fail like that... but yeah, I most certainly can check that. I also further apologize...

Yes, both lines are set, with seemingly random strings of characters. Are they supposed to contain something specific, or am I supposed to leave it as it is? I can...

I suppose I can try to work the rest out myself... I still greatly appreciate all of your help, it has helped me get down to a lot of it....

Update: I have gotten the debugger to attach with VSCode, although it seems nothing is really happening with it. I noticed the ```secure.go``` file was actually around 0.20 kilobytes smaller...