Amber repository contains more parts:
external/subdirectories). Not part of release.
internal/directory, there are development files (
index.htmland its friends). Not part of release.
my). Not part of release. Not pushed to git.
To get your clone, follow this list:
npm install -g amber-cli.
npm installto install dependencies listed in package.json. Used by development tools. See here for more info.
bower installto install dependencies listed in bower.json. Used by Amber in browser. See here for more info.
cd external/amber-dev && npm install && cd ../..to install dependencies of
my/helios, choosing among using your own fork / using the stock version:
git clone email@example.com:<your username>/helios.git my/heliosto use your own fork, or
git clone firstname.lastname@example.org:amber/helios.git my/heliosto use stock version.
cd my/helios && bower install && cd ../...
git clone email@example.com:amber/amber-contrib-legacy.git my/amber-contrib-legacy.
grunt devel. Prepares some transient files.
amber serve. Starts the integrated development server.
Now you should be able to start Amber devlopment page at
http://localhost:4000/internal/ and commit changes you do to disk.
my is in .gitignore, so it is not present after clone,
but because of being in .gitignore, it is "safe haven" to clone other repos into.
Created especially for being able to have your fork of Amber in parallel with
either you fork of Helios, to develop it in parallel, or with stock repo, just to use it.
If you think Amber is not working as expected, You can start by asking on gitter room, IRC or the Mailinglist. Please make sure that you have first checked the following guides:
TODO update these
If the issue can not be resolved you should file an issue on the respective tracker.
Before reporting an issue, try to reduce the issue to the bare minimum required to reproduce it. This allows us to track down and fix the issue in an easier and faster way.
Additionally, you should give us enough information to reproduce the issue. Therefore, include versions of your OS, Amber, Node.js, Grunt, and possibly used libraries as well as sample code. If you don't list the exact steps required to reproduce the issue we won't be able to fix it.
Afterwards, report the issue on one of the following trackers:
If you want to get started developing Amber itself there are a few links to get you started
The Amber development model currently revolves around Pull Requests which are created through GitHub
git push <your repo> <your branchname>
If you created your clone according to the "Setting up your Amber clone", you should run
in Amber directory to start building from CLI.