Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Eugene
    @eistrati
    No, deep-todo-app is one microapp and deep-root-angularjs (aka deep.ng.root) is another microapp. The structure is similar, but the core purpose is different: todo-app is the implementation of todomvc.com, while deep-root-angularjs is the AngularJS (v1) + AngularUI Router.
    4.) Also in https://github.com/MitocGroup/deep-microservices-todo-app. Is "Directory Layout" part up to date with the recent changes?
    Eugene
    @eistrati
    No and yes :) No, it wasn't. We have recently refactored deep-todo-app and I've updated the readme now to reflect those changes: MitocGroup/deep-microservices-todo-app@bf9381d
    Or are "deep.ng.root" and "deep-microservices--app" used together, because I see in "Directory Layout" inside readme that there are some present in deep.ng.root" and not in "deep-microservices--app" but there are some that are not present in deep.ng.root" but present in "deep-microservices--app". Which directory should I edit if I would be using the sample apps as a skeleton? Could be both?
    well, i see how confusing it is for new developers like yourself and i am really sorry that we made it so complicated :(
    we will be working in the next couple of days to simplify and make it easier to get started. deep.ng.root is basically the microapp that loads AngularJS (v1), so in theory you shouldn't do anything there.
    deep-todo-app is the application that you should be looking into and making changes (or using as reference to build new stuff)
    6.) How does the frontend work and talk to the backend. Could dig this up but should be in the docs.
    Eugene
    @eistrati
    Good question. Let's see if I can quickly answer and then include later into our docs... In case of deep-todo-app, the frontend is build in AngularJS, so it works as any other angular apps. The backend is a collection of APIs (either proxied through API Gateway or directly to AWS Lambda), when called, executes specific function - /task/create, /task/delete, /task/retrieve, /task/update, and so on.
    7.) How to create Backend/src sources like SayHello and Backend/src/Task /Create, /Delete, /DeleteCompleted, /MarkAll, /Retrieve, and /Update? I noticed node_modules so maybe through npm install.
    Eugene
    @eistrati
    Again, i think we'll need to add here some more deepify commands that will generate skeleton code. Let us work on this and I'll let you know when it's there ;) For now, it would require manual creation of all the stuff: mkdir -p Backend/src/SayHello (or the other folders) and create the files bootstrap.es6, Handler.es6 and package.json.
    8.) Related to #7. And where are the actual codes (I have to create or pre-created for use) that saves data to DB or how do they (Backend sources) work?
    9.) I see Frontend/package.json and some part of the todomvc are installed through there but how was angularjs installed? Where are the routes, ng-app, and initializing the angular app?
    AngularJS is installed by deep.ng.root, and everything else is here: https://github.com/MitocGroup/deep-microservices-todo-app/tree/master/src/DeepTodo/Frontend/js/app/angular
    In relation to #7 too. For example I'm going to create a backend source that will use some S3 upload from a form in the front-end. How could I do that?
    Eugene
    @eistrati
    yes, you could do that. we actually have this in helloworld sample (although not explained that nicely)
    I think to sum it all up. A step by step guide on how to create the todomvc app from the deep-helloworld(Skeleton) app. AND a simple app from scratch tackling CRUD(DynamoDB), S3 upload. Without using other apps like todomvc and deep-helloworld skeleton.
    I like your idea and we'll consider it. Right now I think it's important to focus on adding deepify commands that will generate some skeleton code for back-end, maybe data and potentially front-end. Next, we'll work on some more videos (tutorial steps) on how to start working with DEEP.
    Do I need the dist or bundled copy of a Nodejs app or frontend app?
    Eugene
    @eistrati
    Well, you don't need nodejs because it comes pre-bundled on AWS Lambda. And we have pre-bundled deep.ng.root (AngularJS v1) for front-end use. We need lots of help to explain that and maybe you can get involved as well ;)
    On deep-todo, deep-hello-world. Are the front-ends Angular2(not yet familiar) already; or just a DEEP structure and implementation?
    The beauty of our approach is that we don't force you to use any particular JS framework. Our team is heavily invested in AngularJS v1 for current projects and our path is something like Frontend/js/app/angular, but you can start with AngularJS v2 instead or maybe React, it's totally up to you. Just make sure that the path is something like Frontend/js/app/angular2 or Frontend/js/app/react ;)
    Wow, that was a lot of questions, but I hope I was clear enough to get you less confused in our mess :) Again, I would like to thank you for your passion and eager to figure it out on your own. We'll be working to simplify and make it more developer friendly, so your input is very welcomed! :)
    thond1st
    @thond1st

    Wow. Thanks a lot @eistrati . These surely did. :)

    They came up while I'm digging into deep-todo and deep-hello-world structure and codes. I guess others will also benefit. :)

    Regarding Frontend Angular1. I was comparing my other old Angular1 apps. DEEP's is totally different.
    For example where is (ng-app="surveyApp") and index.html for Angular1,

    and the structure and codes are different. My guess is the codes are a bit different because of ES6 format.
    But I noticed that an app.js in my Angular1 apps is separated by files or by code blocks in DEEP's.

    I am planning to implement AureliaJS for the frontend. I could use AWS JS SDK for browser with AureliaJS but I would like to integrate Lambda for some use case. This is the reason I'm looking for how does Backend and Front-end communicates and works. Together with the AWS codes or calls in deep-framework.
    In this case. Would I be creating deep.aurelia.root in replacement for deep.ng.root? I also need to discover how to do that. :)

    I am also looking for documentations for
    "TaskModel.createItem(request.data, (err, task)" which I guess is the one calling the deep-framework Lambda code/function to Insert the task title and completed status in DynamoDB
    and
    "this.kernel.get('db').get('Task')" which I guessed defines the Json structure or model from Task.json file.
    If we didn't have the Deep-TODO app. Where could I look for: For example "createItem()" or "deleteItem()" and other functions?

    Eugene
    @eistrati
    no problem. happy to help :)
    although I don't see "ng-app" either, so let me ask internally ;)
    also, let me inquire on "createItem()" and "deleteItem()" -- in theory, it should be here: http://docs.deep.mg/deep-db/ (but I can't find it either)
    Eugene
    @eistrati
    That's why we don't have it in index.html ;)
    Goria Marcel
    @mgoria
    This message was deleted
    https://github.com/ryanfitz/vogels - we are using this library to manage DynamoDB as Active Records
    Eugene
    @eistrati
    @thond1st Would you have some time tomorrow (let's say 11am EST)? I could setup a Google Hangouts session and work through your questions and concerns, as well as involve somebody on our end to answer your AngularJS questions. Please let me know if that would work for you.
    thond1st
    @thond1st

    Thanks @eistrati . If I would be using React as Frontend/js/app/react? Do I still need deep.ng.root or I will create deep.react.root?

    Yeah. That would be great. I'll reserve the question above. :smile:

    Eugene
    @eistrati
    If you wish to use ReactJS instead, then let's definitely join forces and create the deep-root-reactjs together ;)
    send me an email to eugene@mitocgroup.com and I'll send you the details to tomorrow's Google Hangouts
    thond1st
    @thond1st
    That would be awesome. Or also deep-root-aureliajs. AureliaJS is also promising. Sure. I'll send you an email. Thanks.
    Eugene
    @eistrati
    :+1:
    thond1st
    @thond1st
    Hi, I'm just wondering why deep-hello-world web microservice have "deep.ng.root", even though it has no "frontendEngine": ["angular"] in deepkg.json.
    thond1st
    @thond1st
    deep.ng.root is installed during "deepify helloworld". I deleted it before running "deepify server". It also installed itself.
    And this is interesting. I tried to rename "deep.ng.root" folder to "PORdeep.PORng.PORroot". When I ran "deepify server" It treated "PORdeep.PORng.PORroot" as "deep.ng.root".
    Serving file /home/thond1st/deep-todo-app/PORdeep.PORng.PORroot/Frontend/js/app/module/ng-module.js of type application/javascript
    AlexanderC
    @AlexanderC
    Hi @thond1st , in fact any DEEP powered micro application needs an root microservice. We're fetching the angular root microservice by default if there's no other root microservice inside the micro app.
    frontendEngine is by default angular
    As of microservice folder naming (ex. PORdeep.PORng.PORroot instead of deep.ng.root)- it is an expected behaviour, since the deepify is reading the deepkg.json and the folder is, in fact, just a container holding the code.
    AlexanderC
    @AlexanderC
    You can mark the microservice as root by specifying the propertyRoot property
    thond1st
    @thond1st
    Thanks @AlexanderC
    Eugene
    @eistrati
    @/all we are moving to slack - https://mitocgroup.slack.com