Steps to make the final move?

So I think our new JR site is about ready to go... But what I need to know is how do we actually do that? What are the steps to make it take the place of our Ning? We have a non-Ning URL that we've been using for our Ning site and it's the one we want to use for our new JR site. We want to keep our Ning site for about a month more just in case we need anything from it before it disappears.

Your advice and wisdom, please. (Or jut point me in the right direction here on JR if there's already a list of to-do's here somewhere.)

Thanks!
Deb
updated by @icw: 02/01/16 08:09:45AM

There are these docs:

"Ning to Jamroom: Table of Contents"
https://www.jamroom.net/ning-to-jamroom/documentation/contents

in case you haven't seen them before. If you have could you let me know what you are expecting to see (or would like to see) that isn't there please. Im in documentation mode right now.

I am on the road today, but I will take a look at this tomorrow to see if it has everything I'm wondering about and let you know if I still have questions. Thanks, Michael!

Deb

Hi Deb
Basically, all you need to go live with your Jamroom hosted site is to point the registered domain to our servers. To do this, log into the company/website where you registered the domain and set its name servers to the following -

ns1.linode.com
ns2.linode.com
ns3.linode.com
ns4.linode.com
ns5.linode.com

(or as many of those that it has fields for).
Then wait a few hours for this change to propagate around the world (24 hours is recommended but these days its often a lot quicker), then switch your Jamroom hosting to the domain's 'primary' setting. Your JR site is now live!!

Note that if the domain is currently pointing to Ning, be sure to log into your Ning site first and switch it to its 'sub-domain' setting so that it can be accessed at http://yoursite.ning.com, otherwise you might lose access to it when you point the domain away from it.
hth


--
Paul Asher - JR Developer and System Import Specialist

Thanks Paul...

So here's what I think I need to do (in terms that make sense to me), with a few questions thrown in:

1. Set Ning domain to sub-domain. Make sure that is working right.
2. point the registered domain (what we want our JR site to use) to our JR server (details in Paul's message above)
3. Wait 24-48 hours (how will we know how long to wait?)
4. Check to see that our domain has been verified on Mailgun (I've already added our API key)
5. Switch our Jamroom hosting to the domain's 'primary' setting.
6. Do we need to wait after that?
7. Send out a test email to see if it works?
8. Send out emails to all our members with their temporary passwords and wait for them to come rushing in, with no problems at all (LOL).
9. Drink beer and celebrate.

Does that all sound about right?

1) Correct
2) Correct
3) Correct - Wait 3 or 4 hours, say then do a 'WhoIs' at http://whois.domaintools.com. If the resulting name servers are the linode ones there's a good chance that the change has propagated.
4) Switch to Primary setting now
5) Check verification on MG
6) No
7) Correct
8) Correct, but goto the JR ACP first and set the global email field to something like 10 emails/minute so that MG doesn't get hit with 100s of 'new' emails in a short time (watchdog scripts on their servers might think its a spamming attempt). Have you 'KickBox'ed all your emails to verify them? You might want to do that first.
9) Definitely


--
Paul Asher - JR Developer and System Import Specialist

Should I "Kickbox" now? Does it work now? Or before we invite our members to move?

Just looked and the KickBox module is installed on your site but the free daily check of 100 emails isn't enabled (pity as all your user email addresses could have been validated by now). Options -

1) You have ~670 users so if you turn on KB they'll all be validated, for free, in seven days time.
2) Pay KickBox $10 and have them all validated now, in one hit.
3) If you are confident that all or most of your user emails are valid, just go for it.

The reason to be concerned about a lot of invalid emails being sent through MG is that if they suddenly see lots of email bounces, they might think that this is a spamming attempt and block all emails from you, or worse, disable your account.


--
Paul Asher - JR Developer and System Import Specialist

I think there is no red flag over 'spamming' as long as your mailgun invalid bounces are less than 4%... or maybe 5%.

I created a quota (cloned off of my regular member quota) called Invalid Email. In my Kickbox module, I have it set to validate/check 75 or 100 member email addresses per day (I think 100 per day is the maximum for free). I then chose the 'action' for invalid results: to Unsubscribe that member (from notifications and newsletters etc) and to MOVE them to the Invalid email Quota.
Ideally, if all this were done before you go live, you could then send out your temp password Invite to your Member Quota, which would NOT send it to the members in your Invalid Email quota. This would reduce your bounce rate whenever you send out a notice to all your members. Later on you can decide what to do with the members in that invalid email quota.
I would definitely set up that quota and pay the small fee to kickbox-validate all your member addresses right now- then you could totally avoid any spam suspension and subsequent embarrassment when trying to go live.

And yeah definitely send out a test email! I asked SIX trusted members to help me test. I put them temporarily into a NEW Quota I made call TEST. I then sent my test password email notice out to ONLY that quota of six people. I watched them log in from my Dashboard...so cool. They posted and said Hi, this is cool!...lol. They knew they might need to reset their password again later. Then i put them back in the regular member quota and thanked them. This was very reassuring to me before i did the REAL thing with my 5000 members. !


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 10/30/15 11:52:58AM

Sorry - Probably my fault. I put KB on your site after I did the import then must have forgot to tell you about it.


--
Paul Asher - JR Developer and System Import Specialist

Great tips! Thanks so much.