You can run multiple warriors, select different projects for each one you run (or run both with "auto"). I think it's advisable to only run one warrior per IP though, if you're doing many warriors for same project, as otherwise it's a lot easier to get rate-limited by whatever website/service you're helping to archive.

https://github.com/ArchiveTeam/warrior-dockerfile makes it pretty easy to setup.

Not in a single warrior, but you can run multiple warriors. I do this; I have one running Telegrab and one running URLTeam.

Once in a while, a site will tolerate a large number of connections, and since the Warrior VM only supports a concurrency of 6, it can make sense to run multiple warriors on the same project. But this is almost always a bad idea, and many sites will 429 you with a concurrency of anything more than 2 or 3, always check the project-specific IRC channel for concurrency recommendations.

I created a VM and then just duped the VM. Definitely overkill for this purpose, but nicely segregates them out.

Right now I run three instances. Pretty low resource utilization and they're totally segregated into their own instances so just boot them and they run, shut them down and they stop.

Given they're running arbitrary external commands I wanted them kept on their own machines as much as possible.

Not with the Warrior, as far as I'm aware, but you can do it with docker. It's usually the repos with -grab at the end:

https://github.com/orgs/ArchiveTeam/repositories