Is it possible to have frontend in the backend? So, just one server? about angular-sailsjs-boilerplate HOT 9 CLOSED

That is possible and fairly easy to do, but that isn't purpose of this repository.

from angular-sailsjs-boilerplate.

All I need is link. Thanks anyway.

from angular-sailsjs-boilerplate.

@tarlepp Can you help me with this, please. I can not do it alone. I'm trying, but nothing.

from angular-sailsjs-boilerplate.

Basically create new sails application via sails new AwesomeApp then build your frontend side just live in assets folder. There is a lot of examples of that too:

• https://github.com/tarlepp/Taskboard
• https://github.com/cgmartin/sailsjs-angularjs-bootstrap-example

I hope those will help.

from angular-sailsjs-boilerplate.

@tarlepp Thanks, but.

https://github.com/tarlepp/Taskboard doesn't utilize Angular.

And second:

I want utilize your beautiful "angular-sailsjs-boilerplate" in my assets folder. Is this possible? Yes, i know. But I do not understand which steps to perform to carry everything from your folder "frontend" to my "assets".

For this reason I ask your help that sure will solve the problem.

from angular-sailsjs-boilerplate.

Those links contains just an examples how you can manage backend + frontend codes just by using sails.

You cannot use my boilerplate without some serious work because I have disabled all frontend stuff from backend (sails.js). Basically you could use frontend code from the boilerplate, but those will need some serious work also. If I was you I wouldn't do that though.

I would recommend that you create a new sails application and start to write your angular application to assets folder. There should not be any "difficulties" to do that.

from angular-sailsjs-boilerplate.

OK. Thank you very much. I get it.

(In fact I was trying to do, but after hours of nothing, I written here. I'm not good as you.)

Last question: What convinced you to use this technique (backend-frontend) instead of the one you used in the project "taskboard"?

Which one you feel better? And why?

from angular-sailsjs-boilerplate.

With separeted back- and frontend you can easily change those platforms if needed. Eg. I can change backend techstack to some other fairly easy. Also actual frontend server is very light and you can run it via Apache if needed.

Basically this separate aproach gives you much more flexibility on software and server architechture point of view. Common thing is API nothing else. This also allow that you can make multiple frontend applications fairly easy. Or someone other can make that.

I'm converting (rewriting) Taskboard to use separated back- and frontend. But that is work in process... And you should also remember that Taskboard was my first node.js / sails.js application.

from angular-sailsjs-boilerplate.

Ok. I love you.

from angular-sailsjs-boilerplate.