S
swarfrat
Guest
It basically was "controlled public". They were real users, not employees.
The_GuitAar said:As a full stack developer I gotta know, how come the boys/gals didn't use a SQL database table converter to restructure the current database into one that could fit into the new system? Not sure how wise it is to tell all the users "your account is gone".
If it's because of pruning or volume, I would recommend maybe adding a extra col to the existing user table marked as "flagged for transfer". That way you could transfer accounts that the users themselves flagged which could cut down on the processing time.
Honestly, for only 2 people this is a pretty sizable achievement ESPECIALLY if they didn't use any white label code. It makes sense why it took so long, but having in house engineers who know the site inside in out is going to save the company thousands if something goes wrong. Outsourcing gets stupid expensive because they rely on the support charges to stay afloat.
My other recommendation would to be to launch a beta test at beta.warmoth.com for users to poke around and test in Instead of launching it directly to the main site and have to revert. Then when the site is tested, dropping everything in the database and launching to production. Never, EVER, test anything in production. It's more than just a glitchy service, if someone finds a basic SQL injection because one text field wasn't striped you'll end up with someone being able to completely manipulate your backend, including your old site if that server is still attached to the web and not taken to local network only.
Just be careful, love you guys and all you do.
Cagey said:I like what you did with your hair...
JohnnyHardtail said:This domain propagation issue is taking a while. Do you guys know the ip address?
The Aaron said:Here we go...
[youtube]https://youtu.be/u8lFAKSYhvk[/youtube]