zulip

Commit Graph

Author	SHA1	Message	Date
Leo Franchi	501f063426	Replace email_to_domain with split_email_to_domain and resolve_email_to_domain Now that we support email aliases, we have to be careful when going from an email address to a domain that we assume we can use to get a Realm object for. When we care about the Realm's domain, we want to follow any RealmAliases that exist for a certain domain. When we just care about the original email address domain itself, for comparison or other purposes, use split_email_from_domain This removes the ambiguity of having to decide when to use email_to_domain + RealmAlias or just email_to_domain (imported from commit 0e199495502d946ce2e1aae56263e7e8665be4ed)	2013-11-26 10:45:01 -05:00
Jessica McKellar	6dbf7613a1	Supply a name when creating realms. For our populate_db bulk creation, just use the domain. (imported from commit 4fb756f6dfa2d8f90e55822e27891e84168d5d1c)	2013-10-17 13:47:51 -04:00
Kevin Mehall	63cff6eb71	Make populate_db set the is_bot flag on bot accounts. (imported from commit 93a507faa2b19fde05376fd73ed3a65149cfce68)	2013-09-18 16:16:17 -04:00
Tim Abbott	e111a2f9a5	[manual] Rename Django app from zephyr to zerver. This needs to be deployed to both staging and prod at the same off-peak time (and the schema migration run). At the time it is deployed, we need to make a few changes directly in the database: (1) UPDATE django_content_type set app_label='zerver' where app_label='zephyr'; (2) UPDATE south_migrationhistory set app_name='zerver' where app_name='zephyr'; (imported from commit eb3fd719571740189514ef0b884738cb30df1320)	2013-08-06 07:39:36 -04:00

4 Commits