Improve deployment after game update #92

Merged
lucas merged 2 commits from feat/deployment-improvements into master 2023-03-28 20:50:29 +02:00
Owner

Usually the backup created by the first deployment is used for a clean
file to make further deployments from, but when the game is updated,
that is reversed, as now the original file is newer than the backup.

In such a case, we first copy the new file to our backup before
continuing with the deployment.

The current implementation is not fool-proof (e.g. it'll do weird stuff
if users mess with the files manually) and doesn't cover everything. But
it should be enough for the regular use case.

Closes #90.

Usually the backup created by the first deployment is used for a clean file to make further deployments from, but when the game is updated, that is reversed, as now the original file is newer than the backup. In such a case, we first copy the new file to our backup before continuing with the deployment. The current implementation is not fool-proof (e.g. it'll do weird stuff if users mess with the files manually) and doesn't cover everything. But it should be enough for the regular use case. Closes #90.
lucas added this to the DTMM v1.0 + DTMT milestone 2023-03-28 15:33:48 +02:00
lucas added 1 commit 2023-03-28 15:33:49 +02:00
Usually the backup created by the first deployment is used for a clean
file to make further deployments from, but when the game is updated,
that is reversed, as now the original file is newer than the backup.

In such a case, we first copy the new file to our backup before
continuing with the deployment.

The current implementation is not fool-proof (e.g. it'll do weird stuff
if users mess with the files manually) and doesn't cover everything. But
it should be enough for the regular use case.

Closes #90.
lucas added 1 commit 2023-03-28 20:49:45 +02:00
lucas merged commit 0e9903bd6b into master 2023-03-28 20:50:28 +02:00
lucas deleted branch feat/deployment-improvements 2023-03-28 20:50:31 +02:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: bitsquid_dt/dtmt#92
No description provided.