| 07:16:19 | | themadpro quits [Read error: Connection reset by peer] |
| 07:16:20 | | Dragnog quits [Read error: Connection reset by peer] |
| 07:19:15 | | Dragnog joins |
| 07:22:45 | | themadpro (themadpro) joins |
| 09:01:27 | | Dragnog quits [Read error: Connection reset by peer] |
| 09:03:02 | | Dragnog joins |
| 10:09:44 | | drd quits [Remote host closed the connection] |
| 11:25:06 | | VADemon joins |
| 14:34:44 | | Arcorann quits [Ping timeout: 240 seconds] |
| 17:41:24 | | mutantmonkey quits [Ping timeout: 240 seconds] |
| 17:42:01 | | mutantmonkey (mutantmonkey) joins |
| 17:44:06 | | mutantmonkey quits [Remote host closed the connection] |
| 17:44:31 | | mutantmonkey (mutantmonkey) joins |
| 18:04:01 | <themadpro> | Random question: |
| 18:04:24 | <themadpro> | Will the VM warrior ever be fixed? |
| 18:04:29 | <themadpro> | Or Docker4Life? |
| 19:35:54 | <Craigle> | Just think of Docker as a shiny new VM for each project :D |
| 19:36:38 | <Craigle> | But also I believe someone mentioned F usl was working on a new/updated Warrior |
| 19:40:36 | <themadpro> | Well either way |
| 19:40:51 | <themadpro> | Even with Docker, there has to be a better solution that cloning a new repo each time |
| 19:44:00 | | drd joins |
| 19:45:53 | <Craigle> | Honestly, for stuff I run locally, I have an Ubuntu VM I use, and I just keep a copy of my Docker run commands, and update the project name as needed. |
| 19:46:41 | <Craigle> | I'll periodically run a prune as cleanup, but I don't bother naming containers because I may spin up a bunch of them. I just identify what project they are running using the image name |
| 19:47:00 | <@JAA> | Yeah, there will be a new working version of the warrior eventually, also Docker-based. Building a VM wrapper around it isn't difficult though (and it's how the current warrior VM works as well). |
| 19:47:28 | <Craigle> | There's probably a much better/more efficient way to do this, but it gets the job done pretty well for me |
| 19:53:16 | <tech234a> | themadpro: https://archiveteam.org/index.php?title=Running_Archive_Team_Projects_with_Docker |
| 19:53:18 | <@JAA> | I mean, yeah, running Docker directly is better, but the warrior VM is for random Windows desktop users that want to help out and don't have the knowledge or confidence in setting up and using Docker. |
| 20:07:07 | <tech234a> | If we had a "default image" that matched the current priority project, we could probably provide a one-line Docker setup command that users could just copy and paste. |
| 21:49:20 | | VADemon quits [Client Quit] |
| 23:42:51 | | Arcorann (Arcorann) joins |
| 23:43:48 | | Arcorann quits [Remote host closed the connection] |
| 23:44:12 | | Arcorann (Arcorann) joins |