Archive What measures can we put in place to prevent what happened 6/3 from happening again?
- Thread starter BLatta12
- Start date
Archived threads
Madison needs to kill himself. That’s about it
@croot_lord will you post the server in a thread on this board so @BLatta12 and @JerBearr can take a peak at it. They have specced similar things out before and I want the perspective
@croot_lord will you post the server in a thread on this board so @BLatta12 and @JerBearr can take a peak at it. They have specced similar things out before and I want the perspective
I'd rather post the server info on discord just because we have mods in here too.
I sent you a quote for the new server @Croot_Overlord can you check your Gmail and let me know what you think?
I sent you a quote for the new server @Croot_Overlord can you check your Gmail and let me know what you think?
This guys would just know better than me. I’ll just forward the email
No disrespect intended. I hope my post didn't come off that way. I'm just practicing risk management as we would in any engineering task.
I love what you guys have built @croot_lord @JackOfSpeed @Croot_Overlord and glad to be a part of it. Hopefully, you guys see @JerBearr and myself as an asset and not that we are trying to take anything away from what you've got going on.
Im confused, where is that coming from? Being part of a professional team sometimes requires specific directed advice, suggestions, and discussion. I 100% recognize and respect the effort put in by everyone to make this website run, but when giving suggestions, if you beat around the bush and are gentle with things, then misunderstandings can occur. In my opinion it is better to be concise and clear (and come off as a jerk) than it is to be vague and confusing. I never intentionally disrespected anyone, so if anything I've ever said came off disrespectful, I do apologize and I will do my best to be a little easier on my words when in discussion
As for the server, I replied to the email
It doesn’t need to be confusing. You guys have brought some great insight, but sometimes ideas are better presented to your team members/peers as suggestions rather than dictates. If something needs dictated I will handle it.Im confused, where is that coming from? Being part of a professional team sometimes requires specific directed advice, suggestions, and discussion. I 100% recognize and respect the effort put in by everyone to make this website run, but when giving suggestions, if you beat around the bush and are gentle with things, then misunderstandings can occur. In my opinion it is better to be concise and clear (and come off as a jerk) than it is to be vague and confusing. I never intentionally disrespected anyone, so if anything I've ever said came off disrespectful, I do apologize and I will do my best to be a little easier on my words when in discussion
As for the server, I replied to the email
We are on the right track, and this is no big deal just something I wanted to acknowledge.
And by no big deal I mean the point I’m trying to make here. The thing yesterday was a colossal fuck up lol. But I love you @croot_lord
I will say to @BLatta12 question about what we can do to prevent this from happening there is something that would help.
If we had the databases on the same domain, that would help quite a bit. However, it hasn't been a real issue until 6/3 because while the DB is on a different domain, it's still on the same server, so the current domain can access it. It's just confusing to keep in mind that this site uses a DB from a domain that we don't use anymore. I was also unaware of this fact. I was under the impression that when HostGator migrated the website to the new domain, the DB was also.
So when we move to the new server will be time to address this issue. Unfortunately, we cannot do a database migration because it will require downtime, and we do not have a quick process. However, we can develop a quick and repeatable process with the new server. Setting this will help us to reduce downtime as well as avoid the issue we had on 6/3. Right now, we have a lot of data spread out over several domains, and it's difficult to safely know what we can remove and what we can not.
If we had the databases on the same domain, that would help quite a bit. However, it hasn't been a real issue until 6/3 because while the DB is on a different domain, it's still on the same server, so the current domain can access it. It's just confusing to keep in mind that this site uses a DB from a domain that we don't use anymore. I was also unaware of this fact. I was under the impression that when HostGator migrated the website to the new domain, the DB was also.
So when we move to the new server will be time to address this issue. Unfortunately, we cannot do a database migration because it will require downtime, and we do not have a quick process. However, we can develop a quick and repeatable process with the new server. Setting this will help us to reduce downtime as well as avoid the issue we had on 6/3. Right now, we have a lot of data spread out over several domains, and it's difficult to safely know what we can remove and what we can not.