search

leofuturer / eDrops3

The 3rd generation of the eDrops web application.
MIT License
0 stars 0 forks source link

Use a shared email for customer seed data #106

Closed leofuturer closed 1 year ago

leofuturer commented 1 year ago

Currently, two customer accounts in the seed data are using Leo's personal email account. We should change this to a shared account that every team member can access. Please signup for a Gmail account (e.g., edropletscustomerA@gmail.com, or something like that) and use the password commonly used for other testing accounts. Then update the customer.ts to replace the email account for the existing customerA account. We can just delete the customerB account data in the file.

Kenny477 commented 1 year ago

I think maybe we should use a centralized email account (e.g. edropswebsite@gmail.com) and use plus addressing for all our test emails that don't really need real email functionalities. For example, edropswebsite+customerA@gmail.com will be a distinct email from edropswebsite+adminA@gmail.com and both will go to the same inbox.

Kenny477 commented 1 year ago

@leofuturer What centralized email account do you want to use for the website? Should we stick with edropswebsite@gmail.com or change to something else? I believe we use it for a couple of things right now: LetsEncrypt SSL certificates (easy to change), Gitbooks (I think easy to change as well), Shopify (not sure about this).

Also not sure where our credentials for SendGrid and Pusher are floating around. If we choose to centralize everything we should migrate those as well to the chosen account.

And lastly, we currently have emails (edrops.glasspcb@gmail.com, etc.) for each foundry. Do you think we should use plus addressing for those, or will different individuals be using those later on and we should leave the emails as is?

Kenny477 commented 1 year ago

Plus addressing + automatic labelling produces something like this.

For example, any received emails addressed to edropwebsite+customerA@gmail.com will be labelled and sorted under the customerA label. I believe we can make it so some emails received under specific labels are automatically read or hidden if necessary.

Also useful for sorting other emails from the services we use like Shopify.

image
leofuturer commented 1 year ago

@leofuturer What centralized email account do you want to use for the website? Should we stick with edropswebsite@gmail.com or change to something else? I believe we use it for a couple of things right now: LetsEncrypt SSL certificates (easy to change), Gitbooks (I think easy to change as well), Shopify (not sure about this).

Using the + email is a great idea! I didn't know about this feature of Gmail. Yeah, let's use edropswebsite@gmail.com for the centralized email. We

Also not sure where our credentials for SendGrid and Pusher are floating around. If we choose to centralize everything we should migrate those as well to the chosen account.

We are using service@edrops.org for the Pusher. I may need to find the credentials for SendGrid. Afterward, let's migrate to the edropswebsite@gmail.com

And lastly, we currently have emails (edrops.glasspcb@gmail.com, etc.) for each foundry. Do you think we should use plus addressing for those, or will different individuals be using those later on and we should leave the emails as is?

Let's keep them for now. If we find the + email works well, we can probably migrate them later on.