This is an open-source mirror of the code that is running CircleCI's frontend. CircleCI provides powerful Continuous Integration and Deployment with easy setup and maintenance.
Feel free to fork and make contributions. We'll try to get them into the main application.
Want to work with Clojure(Script) full-time? We're hiring.
Dependencies and Setup
Install Node.js and node dependencies:
Note: You can also install leiningen via homebrew with
brew install leiningen
You'll need to install nginx to serve the site over
https - we require local development to use SSL to support using development backends against production APIs in a secure way.
# first, install nginx
brew install nginx
# next, create a self-signed certificate
sudo openssl req -batch -new \
-x509 -newkey rsa:2048 -sha256 -nodes -days 365 \
-subj '/C=US/ST=California/L=San Francisco/O=CircleCI/CN=*.circlehost' \
-keyout star.circlehost.key \
/etc/hosts, add the following line:
If you have access to the backend code, you can also add this line:
Note: Whichever of these you use must be in your
/etc/hosts to get
lein figwheel to run properly (steps in the next section)
You can use foreman (or goreman) to run the frontend and nginx.
foreman start # (or) goreman start
If you're using Docker for Mac, you can also use
docker-compose, in which case you need to start figwheel separately.
docker-compose up -d
lein figwheel dev devcards
To log into using the production backend, visit https://prod.circlehost:4443/dashboard. (
https://prod.circlehost:4443 redirects to outer in a vicious cycle.)
Viewing documentation changes
To see documentation locally you have to compile the docs manifest, like:
lein run -m frontend.tasks.http/precompile-assets
If you add a new document, you will have to re-run that; but if you just change one of the existing documents it should show up with just a page refresh.
Running the Tests
There are two main ways for running tests using the plugin
lein doo. If you wish to run the tests only once, you can do that with
lein doo chrome dev-test once
To have a process watch for changes and run the tests every time you make changes, you can run
lein doo chrome dev-test auto
The default option is
auto, so it will run in that state if you ommit that argument. You can also use
firefox, and a variety of our js enviornments to run the tests on. For full documentation read lein doo's README
To add a test you can either create a new test in an existing ns using
deftest, or create a new ns. However, if you add a new ns it will not automatically be added to the test runner, to do that add it to the list of test ns's in
Asset Compilation Errors
If you are experiencing errors when building assets the following commands may help reset all cached state:
lein cljsbuild once
To test that everything worked, visit https://prod.circlehost:4443/assets/css/app.css and https://prod.circlehost:4443/assets/js/om-dev.js.stefon in your browser.
Production & Development Backends
Now you should have everything you need to start hacking on Circle's frontend!
Visit https://prod.circlehost:4443 for the a production backend with locally build development assets. Again, if you've got access to the backend code (NOTE: it's not open source), you can run it locally on
circlehost:8080. To connect to the development backend, visit https://dev.circlehost:4443. The dev server will default to dev assets, so you don't need the query parameter.
Figwheel runs its own bREPL, which you'll see on the terminal at your
lein figwheel dev. You can also run an additional bREPL over nREPL to connect Cider (or similar) to it. First, connect to the nREPL at localhost:7888. (This port is defined in project.clj.) Then, at the Cider REPL:
Unfortunately for vim-fireplace, Figwheel doesn't expose the repl-env to pass to
:Piggieback in any nice way. (If you'd like to work on making it possible, have a look at
figwheel-sidecar.repl/repl-env. Unfortunately, it takes an entire build map as an argument, rather than just a build ID, as
figwheel-sidecar.repl/cljs-repl does.) However, you can still run an out-of-browser Rhino REPL using
:Piggieback (which vim-fireplace will probably run for you automatically.)
Better Cider Support
I couldn't get the browser repl to work at all using
cemerick.com/piggieback in order to support a lot of its features, including jumping to definitions.
Here's an alternative method for
cider users and possibly others who are dependent on
First, start the
web processes using foreman.
foreman start -f Procfile.alt
Then either start a new repl with
or use the
cider-jack-in command in emacs. Note this is not the
cider-jack-in-clojurescript command. Once the repl is established, execute the following code:
frontend.core> (use 'figwheel-sidecar.repl-api)
Figwheel: Starting server at http://localhost:3449
Figwheel: Watching build - dev
Compiling "resources/public/cljs/out/frontend-dev.js" from ["src-cljs" "test-cljs"]...
Successfully compiled "resources/public/cljs/out/frontend-dev.js" in 5.547 seconds.
Figwheel: Starting CSS Watcher for paths ["resources/assets/css"]
Figwheel: Starting nREPL server on port: 7888
Launching ClojureScript REPL for build: dev
(stop-autobuild) ;; stops Figwheel autobuilder
(start-autobuild [id ...]) ;; starts autobuilder focused on optional ids
(switch-to-build id ...) ;; switches autobuilder to different build
(reset-autobuild) ;; stops, cleans, and starts autobuilder
(reload-config) ;; reloads build config and resets autobuild
(build-once [id ...]) ;; builds source one time
(clean-builds [id ..]) ;; deletes compiled cljs target files
(print-config [id ...]) ;; prints out build configurations
(fig-status) ;; displays current state of system
Switch REPL build focus:
:cljs/quit ;; allows you to switch REPL to another build
Docs: (doc function-name-here)
Exit: Control+C or :cljs/quit
Results: Stored in vars *1, *2, *3, *e holds last exception object
Prompt will show when Figwheel connects to your application
To quit, type: :cljs/quit
Now the middleware should be loaded and emacs
cider navigation should work.
CLJS Dev Tools
Dirac is a fork of Chrome DevTools that works for ClojureScript.
- Google Chrome
- Run the frontend as usual with
- In another terminal,
cdto the project directory and run
./script/devtools.sh. This will open a Chrome window capable of running dev tools.
- Install the Dirac devtools Chrome extension in the instance of Chrome that was started by
devtools.sh. This only needs to be done the first time you use Dirac.
- Click on the Dirac extension icon to the right of the address bar to open the dev tools.
- Toggle CLJS on/off by pressing pgUp/pgDn (fn + up/down arrow on Mac) with focus on the prompt field.