4 ms·
Thanks for replying back to me, I've been having a look and it seems that you guys are very talented. I'm going to start a new project and if this can help me
by heldrida 6y ago
Thanks for replying back to me, I've been having a look and it seems that you guys are very talented.
I'm going to start a new project and if this can help me save time and not have to deal with aws, etc would be great! Depending on cost of course. Hopefully we can get some info in terms of cost.
About the repository/database layer, I found the "store" documentation; just going through things quickly at the moment, but guess that's what store means in the Architecture?
I'll check the examples you've provided and read the documentation properly.
Thank you and good luck!
- asim 6y agoNo worries. Please join the slack at https://slack.m3o.com https://slack.m3o.com if you need help or want to engage with the community. For us Store means key-value or crud data storage. I think if that's what you're calling repository for persistence then that's it. If you're thinking repository as in git then that's a separate connective piece from "source to running" which basically you can do by running the git URL. On the store front. We are working on a data model so we can move beyond key-value which might end up being of interest.
- heldrida 6y agoYes, as in CRUD data storage. I'll join slack. Good luck Asim, the project is kick ass!
- asim 6y agoThank you!
- unneededlogic 6y agoI see that you can point it at a git URL and I see the "running a git source" section of the docs, but I am not seeing how to authenticate to a Github or Gitlab repository if it is not publicly viewable. Do you support that type of authentication?
- asim 6y agoYes. See the doc on private repos https://docs.m3o.com/getting-started/private-repos https://docs.m3o.com/getting-started/private-repos. Hopefully that helps. If not please drop into slack (https://slack.m3o.com https://slack.m3o.com) and we can try help further