1.0.0 • Published 10 years ago

fundbase-portfolios v1.0.0

Weekly downloads
-
License
ISC
Repository
-
Last release
10 years ago

Fundbase Portfolios

Fundbase Portfolios Frontend Application

Installation

This app depends on fundbase-components.

  1. Clone fundbase-components if you don't have it yet.
  2. Clone fundbase-portfolios in the same parent directory.
  3. cd fundbase-portfolios, run npm install (which installs fundbase-components as a dependency)
  4. Run gulp and open http://localhost:8080

Notes

  • The app is built to /build directory.
  • You need to have Rails backend server running at http://localhost:3000 and be signed in to the app.
  • gulp uses gulp-ruby-haml to compile the HAML files, so Ruby and the haml gem have to be runnable (e.g. by swiching to the fundbase RVM gemset)

How do I add new stuff?

  • Templates: add new HAML files to /app/templates/ in whatever dir structure you need. The files can have both .html.haml or .haml extension. In the build the files will be converted to plain HTML and moved into /build/templates/
  • CSS:: add new SCSS files to /app/stylesheets/ in whatever dir structure you need. In the build the files will be converted to plain CSS and moved into /build/stylesheets/
  • Javascript: add new Coffeescript files to /app/javascripts/ in whatever dir structure you need. If you need to include 3rd party libraries or such, you can add a /app/javascript/lib.js manifest file where you can list all the dependencies sprockets style. In the build the files will be converted to plain JS and merged into a single app.js file (please see the documentation in gulpfile.js for additional details)
  • Images: add new images under /app/images/
  • Fonts:: add new fonts under /app/fonts/

TODO

login portfolio index

  • haproxy redirect circleci
  • static server
  • api server env for FE
  • compile or config? tests
  • feature specs should be in FE projects, but there are fabrications
  • same db config, so fabricators will actually work
  • "visit" should not start a server, but point to the redirect/static server

build cycle:

  • push to FE branch
  • pull same branch from API project || integration
  • build - get API project, run API server, run redirect server
  • run browser specs for the respective FE project (spec/features/)
  • PR, merge both projects at once
  • don't run tests after this merge anymore?

https://libraries.io/npm/gulp-cache-buster

1.0.0

10 years ago