Skip to content
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

Node installation #9

Open
hhzl opened this issue Apr 12, 2014 · 4 comments
Open

Node installation #9

hhzl opened this issue Apr 12, 2014 · 4 comments

Comments

@hhzl
Copy link
Member

hhzl commented Apr 12, 2014

I am not sure if we need to tell people how to install nodejs on
http://docs.amber-lang.net/overview/installing.html

http://www.nodejs.org/

does a better job.

What might want to tell people that nodejs is part of the Amber infrastructure and what it is used for in the Amber setup.

@ghost
Copy link

ghost commented Apr 13, 2014

Hannes Hirzel wrote:

I am not sure if we need to tell people how to install nodejs on
http://docs.amber-lang.net/overview/installing.html

http://www.nodejs.org/

does a better job.

What might want to tell people that nodejs is part of the Amber
infrastructure and what it is used for in the Amber setup.

Node is needed for npm to work.

npm installs amber cli in the first place.
It also installs bower.

Node is also needed to run bower, which is needed to include amber itself locally into a project and load its dependencies.

And of course, node is needed to run the amber cli, that is, the development server.

Once browser-based amber project is deployed to production server, node (and npm, and bower) is not needed anymore. It works fine as just a bunch of .htmls, .jss and .csss. But of course, it is most often kept to be able to deploy the newer version of the app. If you know you will not deploy newer version, you can safely remove node etc.

In case you
write a server-side app with amber (even if the amber is primarily meant to be part of browser-based apps), you need node to run it. But this is niche, and would just complicate things.

@hhzl
Copy link
Member Author

hhzl commented Apr 13, 2014

Yes, good summary! These points have to be mentioned in the
documentation --- once we have figured out how to contribute directly.

  1. Node is needed for npm (Node package manager) to work.
  2. With npm you install amber cli in the first place.
  3. With npm you install bower.
  4. Node is also needed to run bower, which is needed to include amber
    itself locally into a project and load its dependencies.
  5. Node is needed to run the amber cli, that is, the development server.

Deployment

Once a browser-based amber project is deployed to aproduction server,
node (and npm, and bower) are not needed anymore. It works fine as
just a collection of .html, .jss and .css files.

But of course, it is most often kept to be able to deploy the newer
version of the app. If you know you will not deploy a newer version,
you can safely remove node etc.

Server side amber app

In case you write a server-side app with amber (even if the amber is
primarily meant to be part of browser-based apps), you need node to
run it. But this is niche, and would just complicate things.

On 4/13/14, Herbert Vojčík [email protected] wrote:

Hannes Hirzel wrote:

I am not sure if we need to tell people how to install nodejs on
http://docs.amber-lang.net/overview/installing.html

http://www.nodejs.org/

does a better job.

What might want to tell people that nodejs is part of the Amber
infrastructure and what it is used for in the Amber setup.

Node is needed for npm to work.

npm installs amber cli in the first place.
It also installs bower.

Node is also needed to run bower, which is needed to include amber itself
locally into a project and load its dependencies.

And of course, node is needed to run the amber cli, that is, the development
server.

Once browser-based amber project is deployed to production server, node (and
npm, and bower) is not needed anymore. It works fine as just a bunch of
.htmls, .jss and .csss. But of course, it is most often kept to be able to
deploy the newer version of the app. If you know you will not deploy newer
version, you can safely remove node etc.

In case you
write a server-side app with amber (even if the amber is primarily meant to
be part of browser-based apps), you need node to run it. But this is niche,
and would just complicate things.


Reply to this email directly or view it on GitHub:
#9 (comment)

@ghost
Copy link

ghost commented Sep 13, 2014

I agree we shouldn't need to include node installation instructions.

@ghost ghost added the enhancement label Sep 14, 2014
@hhzl
Copy link
Member Author

hhzl commented Sep 15, 2014

https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager has a more recent version of nodejs installation instructions than http://docs.amber-lang.net/installing.html. For Ubuntu it now points to https://github.com/nodesource/distributions

hhzl added a commit that referenced this issue Sep 16, 2014
Removed outdated Ubuntu installation instructions, see #9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant