Decided to move TC1 to my main server as I'm running out of resources on the dev server. I will create another VM for devs/beta testers only which will reside where TC1 is currently at.
I'm using an external hard drive instead of the network so I'm hoping this process will take no more then 5 hours.
During this time TC1 will be down.
edit: I had said 2 hours, but looks like it's taking longer, but still, way faster then network speed.
Archived topic from AOV, old topic ID:4293, old post ID:27477
moving TC1 back to old server [done]
- Red Squirrel
- Posts: 29209
- Joined: Wed Dec 18, 2002 12:14 am
- Location: Northern Ontario
- Contact:
moving TC1 back to old server [done]
Honk if you love Jesus, text if you want to meet Him!
- Red Squirrel
- Posts: 29209
- Joined: Wed Dec 18, 2002 12:14 am
- Location: Northern Ontario
- Contact:
moving TC1 back to old server [done]
TC1 is back up.
Now I just need to setup a better sync process then I have currently to make updates as quickly and efficient as possible.
Basically the way things will work now is like this:
1: New content is coded on a private local dev server
2: This new content is merged in on TC2 (private shard, vpn access required)
- It is stress tested by staff.
3: TC2 is synced to TC1 (public test server)
- It is now tested further by staff as well as any players who happen to go on.
4: TC1 is synced to live, and a publish is posted.
This new process will help make things more efficient during the shard revamp as specialized/emergency updates can be performed directly on TC1 without having to worry about putting some TC2 (revamp) updates to live. TC1 will only ever be synced when TC2 data is planned to go into production shortly.
Archived topic from AOV, old topic ID:4293, old post ID:27489
Now I just need to setup a better sync process then I have currently to make updates as quickly and efficient as possible.
Basically the way things will work now is like this:
1: New content is coded on a private local dev server
2: This new content is merged in on TC2 (private shard, vpn access required)
- It is stress tested by staff.
3: TC2 is synced to TC1 (public test server)
- It is now tested further by staff as well as any players who happen to go on.
4: TC1 is synced to live, and a publish is posted.
This new process will help make things more efficient during the shard revamp as specialized/emergency updates can be performed directly on TC1 without having to worry about putting some TC2 (revamp) updates to live. TC1 will only ever be synced when TC2 data is planned to go into production shortly.
Archived topic from AOV, old topic ID:4293, old post ID:27489
Honk if you love Jesus, text if you want to meet Him!