Next milestone discussion 🔥

[jmaicaaan]

What I have on mind right now are these things:

• Full featured CMS support (probably let's give the demo site a little bit interaction)
• Add a place in the client side to display the current version deployed (from the prev. conversation with @john20xdoe)
• Email support (do we need to have this already?)
• Make the migrations use Table instead of raw query for better readability (?)

Also, another feature into the list component in the client, that will automatically request to the specified endpoint? 🤔

cc: @john20xdoe @cedrickmandocdoc

[jmaicaaan]

If you agree with the email support, we'll prolly add the reset password support also 🙆‍♂️

[john20xdoe]

+1 for the email. For email support, currently we can limit it to basic notifications. Account-related (important. required):

• Email verification (for registration and change email)
• Reset password
• Login notifications ...

Subscribed notifications

• event notifications that can be subscribed on or off
• Unsubscribe notifications (has a standalone page) ...

NOTE: once we enable email, this also involves proper formatting and email headers so that our emails will not be flagged as spam.

BTW, last time I checked. there is a free tier addon for SendMail in Heroku. I still had one in my old app (circa 2015) that allows free sending without a SendMail acct. But last time I created a new app, using the same addon required a new SendMail Account (and registering for a SendMail account nowadays require a short questionnaire for them to verify your website if it is production-grade. I had my new SendMail acct banned when I mentioned I'm still under development.)

Perhaps you can try adding the addon. If the SendMail account gets banned, I'll try to find the credentiials for my old Heroku-related autoaccount that may still be active for dev.

[john20xdoe]

For the CMS support, we could maybe create the client-side from our vue.js template from @jm-4life . Though I',m not sure if we should create a new repo for it or just include it with gauntlet?

[john20xdoe]

Oh wait, nevermind about the vue. We already have angular here, right?

[jmaicaaan]

I'm not sure if we would like to have the subscribed notification part already. But the Account related features is a must 👍

What is the difference between the SendMail you are mentioning and also this SendGrid?

For the CMS, we already have set up the angular here. The vue-template, we could work on it to another repository soon. You could see in our demo site a preview 🥂

[john20xdoe]

Yes, subscriptions are nice-to-have but not required.

Oops, I stand corrected, I do mean SendGrid hahaha. Been awhile since I've used it...

[john20xdoe]

The configuration for email credentials will also be managed similar to the database.. perhaps again via environment variables.

BTW using SendGrid is not required. For basic sending, we can also test just by using Gmail's POP or IMAP credentials. https://support.google.com/mail/answer/7104828?hl=en PRobably using aliases like ultrarangersPLUStestnotifsATgmail.com

[jmaicaaan]

Is there any difference in using SendGrid rather than Gmail?

[john20xdoe]

SendGrid is much more reliable, and better designed to send mass emails (it's been recognized as non-spam, unless of course the actual email has questionable content). For GMail, we can use it for dev purposes only since it is already set up. However, we shouldn't use it for prod since it doesn't look official, plus free GMail has limits for sending mass emails to prevent abuse and spam (unless setup with GSuite), which will sometimes result in random failures when sending. Also, using the Gmail IMAP and POP outside of email clients will raise an alert in your account for "Less secure apps" https://support.google.com/accounts/answer/6010255?hl=en

[jmaicaaan]

Thanks for the info 👍

Let's just wait for @cedrickmandocdoc if he has any thing to suggest in our next milestone beside from the email features!

[ghost]

Yes email support is good. For migrations using Table is good also. For the table that automatically request, it is also good. Let's do this all.

[ghost]

How about we add this on our list:

• Continuous Deployment for different environments (testing, staging, production)
• Provide OAuth in the server

[john20xdoe]

For CD, we can setup Heroku pipelines (test, staging) in the current Heroku demo app, or maybe the workflows in CircleCI (I don't know how to set up CircleCi for now). Although, I think staging and production is not that important unless we are actually creating a full non-demo app made from gauntlet (the purpose of staging and prod are for other users).

For test env though, it is necessary to run tests, but not unit tests (that is what CircleCI is for). The test env is for integration and UI tests, again of an app implementing gauntlet.

[jmaicaaan]

I think other environments such as staging and prod is not necessary for us to work on. But the test environment is a must.

Summarizing the discussion here is the list of items I have for our next milestone

• CMS Demo (login, dashboard, profile & reset password pages)
• Email support (we can the email provider from the slack last time if you guys remembered. Please add it here)
• A place in the UI where we see the deployed version

Some things are not necessary yet. What are yout thoughts? If everything's good, I'll create the issues/tickets for it 🔥

[ghost]

Everything is good to me haha, Lets get this done. And also remember the issue in the provider it causes circular import I guess in the case of entities, repositories etc having exported in index. But I don't know the real issue. I do have a suggestion, putting the entities in common? yeah I just realized right now what you said to me last time about that, that it should be in common is right.

[jmaicaaan]

What have you realized in the entities part? Hmm, that would change again a few things in our structure.

[jmaicaaan]

Anyways, I've added the new tickets both client and server. Here is the new milestone 🔥