[DiscordArchive] is this hosting and using hte vm on the same machine?
[DiscordArchive] is this hosting and using hte vm on the same machine?
Original source
is this hosting and using hte vm on the same machine?
rektbyfaith
08-22-2023, 12:16 AM #1Archived author: Ĝ̷̳r̸̹͊a̷̜̚k̴̞̔ • Posted: 2023-08-22T00:16:16.998000+00:00
Original source
is this hosting and using hte vm on the same machine?
Original source
Yeah, I sadly don't know how because I only ever used vsphere and proxmox.
rektbyfaith
08-22-2023, 12:16 AM #2Archived author: Revision • Posted: 2023-08-22T00:16:32.330000+00:00
Original source
Yeah, I sadly don't know how because I only ever used vsphere and proxmox.
Original source
I know I was messing around with cockpit and the available plugin to manage kvm but it was still a confusing mess to me.
rektbyfaith
08-22-2023, 12:17 AM #3Archived author: Revision • Posted: 2023-08-22T00:17:27.908000+00:00
Original source
I know I was messing around with cockpit and the available plugin to manage kvm but it was still a confusing mess to me.
Original source
just back to my original issue, cause youll all likely be off to bed by the time i get to the next step, do i have to go to the version of teh squash, or can i just jump to current version do that update then do my fork/modules?
rektbyfaith
08-22-2023, 12:18 AM #4Archived author: Ĝ̷̳r̸̹͊a̷̜̚k̴̞̔ • Posted: 2023-08-22T00:18:05.536000+00:00
Original source
just back to my original issue, cause youll all likely be off to bed by the time i get to the next step, do i have to go to the version of teh squash, or can i just jump to current version do that update then do my fork/modules?
Original source
After you run through the commit before the squash, it should be safe to move to the newest commit next. I say should to protect myself even if I am sure it won't cause any issues to do so.
rektbyfaith
08-22-2023, 12:18 AM #5Archived author: Revision • Posted: 2023-08-22T00:18:48.547000+00:00
Original source
After you run through the commit before the squash, it should be safe to move to the newest commit next. I say should to protect myself even if I am sure it won't cause any issues to do so.
Original source
cool
rektbyfaith
08-22-2023, 12:19 AM #6Archived author: Ĝ̷̳r̸̹͊a̷̜̚k̴̞̔ • Posted: 2023-08-22T00:19:20.620000+00:00
Original source
cool
Original source
that is newest npcbots not AC
rektbyfaith
08-22-2023, 12:19 AM #7Archived author: Rymercyble • Posted: 2023-08-22T00:19:37.373000+00:00
Original source
that is newest npcbots not AC
Original source
oh if that works to then even better
rektbyfaith
08-22-2023, 12:19 AM #8Archived author: Ĝ̷̳r̸̹͊a̷̜̚k̴̞̔ • Posted: 2023-08-22T00:19:52.001000+00:00
Original source
oh if that works to then even better
Original source
maybe it wont but u cant go to newest AC bcs that could be incompatible with npcbots
rektbyfaith
08-22-2023, 12:20 AM #9Archived author: Rymercyble • Posted: 2023-08-22T00:20:19.569000+00:00
Original source
maybe it wont but u cant go to newest AC bcs that could be incompatible with npcbots
Original source
The AC master gets merged into npcbots once a week, and you can also merge it yourself if you know how to (or add it as a remote and merge it that way), so it's using a decently new version of AC.
rektbyfaith
08-22-2023, 12:21 AM #10Archived author: Revision • Posted: 2023-08-22T00:21:01.760000+00:00
Original source
The AC master gets merged into npcbots once a week, and you can also merge it yourself if you know how to (or add it as a remote and merge it that way), so it's using a decently new version of AC.
1 Guest(s)
1 Guest(s)