{"id":32513017,"url":"https://github.com/stav/timelion-carbon","last_synced_at":"2026-02-24T12:01:41.077Z","repository":{"id":140485782,"uuid":"21079520","full_name":"stav/timelion-carbon","owner":"stav","description":"An AngularJS log of drugs my dog was on.","archived":false,"fork":false,"pushed_at":"2015-09-23T19:46:59.000Z","size":1248,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"master","last_synced_at":"2025-10-27T22:49:37.407Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"HTML","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/stav.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2014-06-21T21:43:38.000Z","updated_at":"2015-05-29T16:40:18.000Z","dependencies_parsed_at":"2023-03-13T09:21:09.092Z","dependency_job_id":null,"html_url":"https://github.com/stav/timelion-carbon","commit_stats":null,"previous_names":[],"tags_count":1,"template":false,"template_full_name":null,"purl":"pkg:github/stav/timelion-carbon","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/stav%2Ftimelion-carbon","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/stav%2Ftimelion-carbon/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/stav%2Ftimelion-carbon/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/stav%2Ftimelion-carbon/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/stav","download_url":"https://codeload.github.com/stav/timelion-carbon/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/stav%2Ftimelion-carbon/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29781209,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-24T10:45:18.109Z","status":"ssl_error","status_checked_at":"2026-02-24T10:45:09.911Z","response_time":75,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-10-27T22:49:28.505Z","updated_at":"2026-02-24T12:01:41.072Z","avatar_url":"https://github.com/stav.png","language":"HTML","funding_links":[],"categories":[],"sub_categories":[],"readme":"\ntimelion-carbon\n===============\n\nA log of drugs our dog was on during his recovery.\n\nThis project is based on the AngularJS [seed application](https://github.com/angular/angular-seed)\n\"skeleton\" for a typical [AngularJS](http://angularjs.org/) web app which is useful\nto quickly bootstrap angular webapp projects and dev environments.\n\n## Getting Started\n\nTo get started using `timelion/carbon`, clone this repository and install the\ndependencies:\n\n### Prerequisites\n\nOf course you'll need [git][git] to clone the repository and a number of\n[node.js](http://nodejs.org/) tools like `npm` to initialize and test.\n\n### Clone the repository\n\n```\ngit clone https://github.com/stav/timelion-carbon.git\ncd timelion-carbon\n```\n\n### Install Dependencies\n\nThere are two kinds of dependencies in this project: tools and angular framework\ncode.  The tools help manage and test the application.\n\n* We get the tools we depend upon via `npm`, the [node package manager][npm].\n* We get the client code via `bower`, a [client-side code package manager][bower].\n\n`npm` is preconfigured to automatically run `bower` so we can simply do:\n\n```\nnpm install\n```\n\nBehind the scenes this will also call `bower install`.  You should find that you\nhave two new folders in your project.\n\n* `node_modules` - contains the npm packages for the tools we need\n* `app/bower_components` - contains the angular framework files\n\n*Note that the `bower_components` folder would normally be installed in the root\nfolder but angular-seed changes this location through the `.bowerrc` file.  Putting\nit in the app folder makes it easier to serve the files by a webserver.*\n\n### Run the Application\n\nThe project is configured with a simple development web server.  The simplest way\nto start this server is:\n\n```\nnpm start\n```\n\nNow browse to the app at `http://localhost:8000/app/index.html`.\n\n## Directory Layout\n\n    app/                --\u003e all of the files to be used in production\n      css/              --\u003e css files\n        app.css         --\u003e default stylesheet\n      img/              --\u003e image files\n      index.html        --\u003e app layout file (the main html template file of the app)\n      index-async.html  --\u003e just like index.html, but loads js files asynchronously\n      js/               --\u003e javascript files\n        app.js          --\u003e application\n        controllers.js  --\u003e application controllers\n        directives.js   --\u003e application directives\n        filters.js      --\u003e custom angular filters\n        services.js     --\u003e custom angular services\n      partials/             --\u003e angular view partials (partial html templates)\n        partial1.html\n        partial2.html\n\n    test/               --\u003e test config and source files\n      protractor-conf.js    --\u003e config file for running e2e tests with Protractor\n      e2e/                  --\u003e end-to-end specs\n        scenarios.js\n      karma.conf.js         --\u003e config file for running unit tests with Karma\n      unit/                 --\u003e unit level specs/tests\n        controllersSpec.js      --\u003e specs for controllers\n        directivessSpec.js      --\u003e specs for directives\n        filtersSpec.js          --\u003e specs for filters\n        servicesSpec.js         --\u003e specs for services\n\n## Testing\n\nThere are two kinds of tests in the angular-seed application: _Unit_ tests and\n_End to End_ tests.\n\n### Running Unit Tests\n\nThe angular-seed app comes preconfigured with unit tests. These are written in\n[Jasmine][jasmine], which we run with the [Karma Test Runner][karma]. We provide a Karma\nconfiguration file to run them.\n\n* the configuration is found at `test/karma.conf.js`\n* the unit tests are found in `test/unit/`.\n\nThe easiest way to run the unit tests is to use the supplied npm script:\n\n```\nnpm test\n```\n\nThis script will start the Karma test runner to execute the unit tests. Moreover, Karma will sit and\nwatch the source and test files for changes and then re-run the tests whenever any of them change.\nThis is the recommended strategy; if your unit tests are being run every time you save a file then\nyou receive instant feedback on any changes that break the expected code functionality.\n\nYou can also ask Karma to do a single run of the tests and then exit.  This is useful if you want to\ncheck that a particular version of the code is operating as expected.  The project contains a\npredefined script to do this:\n\n```\nnpm run test-single-run\n```\n\n\n### End to end testing\n\nThe angular-seed app comes with end-to-end tests, again written in [Jasmine][jasmine]. These tests\nare run with the [Protractor][protractor] End-to-End test runner.  It uses native events and has\nspecial features for Angular applications.\n\n* the configuration is found at `test/protractor-conf.js`\n* the end-to-end tests are found in `test/e2e/`\n\nProtractor simulates interaction with our web app and verifies that the application responds\ncorrectly. Therefore, our web server needs to be serving up the application, so that Protractor\ncan interact with it.\n\n```\nnpm start\n```\n\nIn addition, since Protractor is built upon WebDriver we need to install this.  The angular-seed\nproject comes with a predefined script to do this:\n\n```\nnpm run update-webdriver\n```\n\nThis will download and install the latest version of the stand-alone WebDriver tool.\n\nOnce you have ensured that the development web server hosting our application is up and running\nand WebDriver is updated, you can run the end-to-end tests using the supplied npm script:\n\n```\nnpm run protractor\n```\n\nThis script will execute the end-to-end tests against the application being hosted on the\ndevelopment server.\n\n\n## Updating Angular\n\nPreviously we recommended that you merge in changes to angular-seed into your own fork of the project.\nNow that the angular framework library code and tools are acquired through package managers (npm and\nbower) you can use these tools instead to update the dependencies.\n\nYou can update the tool dependencies by running:\n\n```\nnpm update\n```\n\nThis will find the latest versions that match the version ranges specified in the `package.json` file.\n\nYou can update the Angular dependencies by running:\n\n```\nbower update\n```\n\nThis will find the latest versions that match the version ranges specified in the `bower.json` file.\n\n\n## Loading Angular Asynchronously\n\nThe angular-seed project supports loading the framework and application scripts asynchronously.  The\nspecial `index-async.html` is designed to support this style of loading.  For it to work you must\ninject a piece of Angular JavaScript into the HTML page.  The project has a predefined script to help\ndo this.\n\n```\nnpm run update-index-async\n```\n\nThis will copy the contents of the `angular-loader.js` library file into the `index-async.html` page.\nYou can run this every time you update the version of Angular that you are using.\n\n\n## Serving the Application Files\n\nWhile angular is client-side-only technology and it's possible to create angular webapps that\ndon't require a backend server at all, we recommend serving the project files using a local\nwebserver during development to avoid issues with security restrictions (sandbox) in browsers. The\nsandbox implementation varies between browsers, but quite often prevents things like cookies, xhr,\netc to function properly when an html page is opened via `file://` scheme instead of `http://`.\n\n\n### Running the App during Development\n\nThe angular-seed project comes preconfigured with a local development webserver.  It is a node.js\ntool called [http-server][http-server].  You can start this webserver with `npm start` but you may choose to\ninstall the tool globally:\n\n```\nsudo npm install -g http-server\n```\n\nThen you can start your own development web server to serve static files from a folder by\nrunning:\n\n```\nhttp-server -a localhost -p 8000\n```\n\nAlternatively, you can choose to configure your own webserver, such as apache or nginx. Just\nconfigure your server to serve the files under the `app/` directory.\n\n\n### Running the App in Production\n\nThis really depends on how complex your app is and the overall infrastructure of your system, but\nthe general rule is that all you need in production are all the files under the `app/` directory.\nEverything else should be omitted.\n\nAngular apps are really just a bunch of static html, css and js files that just need to be hosted\nsomewhere they can be accessed by browsers.\n\nIf your Angular app is talking to the backend server via xhr or other means, you need to figure\nout what is the best way to host the static files to comply with the same origin policy if\napplicable. Usually this is done by hosting the files by the backend server or through\nreverse-proxying the backend server(s) and webserver(s).\n\n\n## Continuous Integration\n\n### Travis CI\n\n[Travis CI][travis] is a continuous integration service, which can monitor GitHub for new commits\nto your repository and execute scripts such as building the app or running tests. The angular-seed\nproject contains a Travis configuration file, `.travis.yml`, which will cause Travis to run your\ntests when you push to GitHub.\n\nYou will need to enable the integration between Travis and GitHub. See the Travis website for more\ninstruction on how to do this.\n\n### CloudBees\n\nCloudBees have provided a CI/deployment setup:\n\n\u003ca href=\"https://grandcentral.cloudbees.com/?CB_clickstart=https://raw.github.com/CloudBees-community/angular-js-clickstart/master/clickstart.json\"\u003e\n\u003cimg src=\"https://d3ko533tu1ozfq.cloudfront.net/clickstart/deployInstantly.png\"/\u003e\u003c/a\u003e\n\nIf you run this, you will get a cloned version of this repo to start working on in a private git repo,\nalong with a CI service (in Jenkins) hosted that will run unit and end to end tests in both Firefox and Chrome.\n\n\n## Contact\n\nFor more information on AngularJS please check out http://angularjs.org/\n\n[git]: http://git-scm.com/\n[bower]: http://bower.io\n[npm]: https://www.npmjs.org/\n[node]: http://nodejs.org\n[protractor]: https://github.com/angular/protractor\n[jasmine]: http://jasmine.github.io\n[karma]: http://karma-runner.github.io\n[travis]: https://travis-ci.org/\n[http-server]: https://github.com/nodeapps/http-server\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fstav%2Ftimelion-carbon","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fstav%2Ftimelion-carbon","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fstav%2Ftimelion-carbon/lists"}