How you update your pack with the monthly updates?

MrTitan

Knight
Customer
Hi guys, I just wonder how you keep your project updated. How you maintain your server with the latest updates?
I have many modifications in my server and I always struggle to update to version where many things has been changed like core/html files and etc.
 
Я может слишком стар, но я смотрю каждую ревизию и заменяю соответствующие строки/добавляю в ручную, которые автоматически не обновились в связи с изменениями.
 
It takes me about 1 minute: This is the process I’ve always followed for keeping packs in sync.

I have the following workplace folders in my IDE, all of which are uploaded to a Subversion/SVN server:

  • main (the main project)
  • revision (same revision as the main, but clean)
  • vanilla (Lucera's Subversion)
Here’s the workflow, assuming main and revision are on the same revision (last synced):
  1. I update vanilla to the latest revision (head).
  2. I delete authserver and gameserver from revision.
  3. I replace them with the latest authserver and gameserver from vanilla.
  4. Now, I generate the diff patch on revision. I export it to apply it to main.
  5. I commit the revision folder with the latest changes, commenting: "Revision: 445".
  6. I import the diff patch to main and commit it, commenting: "Main: 445". Before importing the diff patch, you need to manually mass replace /config/default_english/ with /config/. Also, you’ll need to manually copy and paste the .jar files into the main.
If there’s any patch mismatch, I simply uncheck the files with errors, make a note of them, and apply those manually later (while I auto import the rest). Using this process, it typically takes between one and a few minutes. I usually update every few days, so there’s never too much to apply at once. Keeping the server up to date is good—when you avoid applying too many changes at once, it becomes much easier to trace issues and identify which revision caused them.

I hope this makes the process clear.
For those looking to replicate this, you can use VisualSVN for Windows (it’s free). Personally, I always run a Subversion server on a cheap VPS to handle main and revisionI use Mac.
 
Last edited:
It takes me about 1 minute: This is the process I’ve always followed for keeping packs in sync.

I have the following workplace folders in my IDE, all of which are uploaded to a Subversion/SVN server:

  • main (the main project)
  • revision (current revision synced with main)
  • vanilla (Lucera's Subversion)
Here’s the workflow, assuming main and revision are on the same revision (last synced):
  1. I update vanilla to the latest revision (head).
  2. I delete authserver and gameserver from revision.
  3. I replace them with the latest authserver and gameserver from vanilla.
  4. Now, I generate the diff patch on revision. I export it to apply it to main.
  5. I commit the revision folder with the latest changes, commenting: "Revision: 445".
  6. I import the diff patch to main and commit it, commenting: "Main: 445". Before importing the diff patch, you need to manually mass replace /config/default_english/ with /config/. Also, you’ll need to manually copy and paste the .jar files into the main.
If there’s any patch mismatch, I simply uncheck the files with errors, make a note of them, and apply those manually later (while I auto import the rest). Using this process, it typically takes between one and a few minutes. I usually update every few days, so there’s never too much to apply at once. Keeping the server up to date is good—when you avoid applying too many changes at once, it becomes much easier to trace issues and identify which revision caused them.

I hope this makes the process clear.
For those looking to replicate this, you can use VisualSVN for Windows (it’s free). Personally, I always run a Subversion server on a cheap VPS to handle main and revisionI use Mac.
Thats.... amazing. Thanks Trance!
 
Вношу изменения вручную в каждый возможный файл в соответствии с изменениями в каждой ревизии
 
имею гит, вношу изменения по мере необходимости обновления, в среднем где то раз в 2 недели, переношу вручную из каждого коммита прям отсюда
1732901339184.webp


обязательно записываю номер ревы к себе в коммиты
1732901433249.webp
 
Back
Top