New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connect master branch to AWS Amplify or Netlify #47
Comments
@QjStout g'day. have you started this task? I have been working with netlify a bit, and almost done with the route/nav issue. let's pair up and get it done, if it's OK. |
Hey @kimchirice, I'm going to do this one man. It won't take me long, I just haven't had a chance to get to it yet. |
Not going with AWS. There is no ability to set hard budget limits and I could rack up 10's of thousands in debt in less than an hour. |
cool, man. I reckon going forward with Netlify is what we need at the moment. |
Hey @kimchirice, passing this to you now if that's okay still |
Thanks @kimchirice, I appreciate it. |
Sounds good, @kimchirice. Thanks. |
sorry for the late update. Engramar and myself worked together yesterday, and managed to have our repo built and hosted on the Netlify. it seems has been working OK since then. NOTEthe deployment on Netlify is done with my personal account, after discussed with Engramar, we agreed to process this with my personal account for now. once we sort out the other issue of CI assigned to me, we will then transfer the ownership to Engramar for this stag, it is OK to close this issue. what do you gents think? |
Looks good @kimchirice. |
I think we are good to close this @kimchirice |
Engramar would like this project to be a live development environment. This will act as a live staging area, directly updated from the master branch.
The text was updated successfully, but these errors were encountered: