[DiscordArchive] do you deploy local code changes at all and waht does that look like?
[DiscordArchive] do you deploy local code changes at all and waht does that look like?
Original source
do you deploy local code changes at all and waht does that look like?
rektbyfaith
08-24-2025, 07:11 AM #1Archived author: Exlex • Posted: 2025-08-24T07:11:26.560000+00:00
Original source
do you deploy local code changes at all and waht does that look like?
Original source
Yeah, mine's local only and I didn't change the directory it builds to from default. So if I make changes and run the build command, it replaces what I previously had.
rektbyfaith
08-24-2025, 07:13 AM #2Archived author: Spargel • Posted: 2025-08-24T07:13:13.049000+00:00
Original source
Yeah, mine's local only and I didn't change the directory it builds to from default. So if I make changes and run the build command, it replaces what I previously had.
Original source
Since mine's only for me, I didn't bother with having the output somewhere else for multiple versions.
rektbyfaith
08-24-2025, 07:14 AM #3Archived author: Spargel • Posted: 2025-08-24T07:14:13.889000+00:00
Original source
Since mine's only for me, I didn't bother with having the output somewhere else for multiple versions.
Original source
So, with above workflow, how do I make it so that when I run it it automatically generates appropriate v2022 solution file (if it doesn't exist), and it is configured to automatically point towards that generated source?
The idea being that I can make code changes while working on bugs, then when i am ready to test, I can run somethign like `./acore.sh compiler build` to build that source and start server again with my new changes?
rektbyfaith
08-24-2025, 07:17 AM #4Archived author: Exlex • Posted: 2025-08-24T07:17:06.930000+00:00
Original source
So, with above workflow, how do I make it so that when I run it it automatically generates appropriate v2022 solution file (if it doesn't exist), and it is configured to automatically point towards that generated source?
The idea being that I can make code changes while working on bugs, then when i am ready to test, I can run somethign like `./acore.sh compiler build` to build that source and start server again with my new changes?
Original source
it seems that `./acore.sh` already does everything else, for me it's just understanding how to get my dev workflow (of building my vs2022 sln that i am actively working on) so that I can basically make a fix, deploy, make another fix, deploy etc
rektbyfaith
08-24-2025, 07:18 AM #5Archived author: Exlex • Posted: 2025-08-24T07:18:43.860000+00:00
Original source
it seems that `./acore.sh` already does everything else, for me it's just understanding how to get my dev workflow (of building my vs2022 sln that i am actively working on) so that I can basically make a fix, deploy, make another fix, deploy etc
Original source
That I do not know. I don't use the main Visual Studio with this, just VSCode for editing.
rektbyfaith
08-24-2025, 07:19 AM #6Archived author: Spargel • Posted: 2025-08-24T07:19:12.810000+00:00
Original source
That I do not know. I don't use the main Visual Studio with this, just VSCode for editing.
Original source
yeah good point i suppose i could just do that. Maybe am making things complicated for myself for no reason. There is no need to use VS in this situation as `compiler build` already does that for me
rektbyfaith
08-24-2025, 07:20 AM #7Archived author: Exlex • Posted: 2025-08-24T07:20:15.512000+00:00
Original source
yeah good point i suppose i could just do that. Maybe am making things complicated for myself for no reason. There is no need to use VS in this situation as `compiler build` already does that for me
Original source
so you just make changes in `/src` folder using vscode, then when you're ready to see changes you just run your above command?
rektbyfaith
08-24-2025, 07:20 AM #8Archived author: Exlex • Posted: 2025-08-24T07:20:56.583000+00:00
Original source
so you just make changes in `/src` folder using vscode, then when you're ready to see changes you just run your above command?
Original source
Yep. Sometimes repeatedly if I messed something up and have to fix it first, but the process is simple. Same for switching between branches in the core/modules, just run the build command again after doing so.
rektbyfaith
08-24-2025, 07:22 AM #9Archived author: Spargel • Posted: 2025-08-24T07:22:12.627000+00:00
Original source
Yep. Sometimes repeatedly if I messed something up and have to fix it first, but the process is simple. Same for switching between branches in the core/modules, just run the build command again after doing so.
Original source
And you should rarely need to `clean`, but it's just `./acore.sh compiler clean` when you do.
rektbyfaith
08-24-2025, 07:23 AM #10Archived author: Spargel • Posted: 2025-08-24T07:23:41.245000+00:00
Original source
And you should rarely need to `clean`, but it's just `./acore.sh compiler clean` when you do.
1 Guest(s)
1 Guest(s)