To run Flow:
docker-compose up --build -d && docker-compose logs -f
Flow should be running here and you can login with user "[email protected]"
You also have the appengine admin console here
The Docker-Compose environment will have:
- A fake s3 server.
- A fake flow services, that always returns 200.
- The dev environment.
It downloads a prepopulated database from https://s3-eu-west-1.amazonaws.com/akvoflow/test-data/local_db.bin if there is none.
It will use the dev appengine-web.xml if there is none.
See the devserver.sh for more details.
Once Flow is started, any changes in the Dashboard folder will trigger a build of the UI code, except for the ClojureScript bit.
If you are going to work on the ClojureScript side, you can run a watch process with:
docker-compose exec -u akvo akvo-flow /bin/bash -c "cd Dashboard/app/cljs && lein watch"
Or run the commands from a terminal inside the container:
docker-compose exec -u akvo akvo-flow /bin/bash
cd Dashboard/app/cljs
lein watch
The client-side (JS) code is linted using Eslint. It is recommended to install an Eslint plugin in your editor to display linting errors in realtime while making changes to the source code.
See here for a list of intergrations/plugins for various editors: https://eslint.org/docs/user-guide/integrations#editors
The appengine dev server is started in debug mode, listening in port 5005.
It is expected that your IDE understand the Maven pom and that it compiles the Java classes to the right place.
After you IDE compiles the classes, the dev server should refresh the webcontext. Due to some Mac performance issues with Docker, the refresh interval is 20 secs instead of the default 5 secs. You can change the scan interval by setting the property GAE_FULL_SCAN_SECS to the desired value. You can also trigger a reload hitting the reload url.
If you need to restart the server:
docker-compose exec -u akvo -d akvo-flow /bin/bash -c "cd GAE && mvn appengine:stop appengine:run >> ./target/build.log"
Remember that you also can run those commands from a terminal inside the container.
docker-compose stop
docker-compose down
rm -rf GAE/target
If you want to use a configuration different from the dev one, checkout the akvo-flow-server-config directory into .. and run:
switch_tenant.sh akvoflowsandbox
To switch back to the dev setup:
switch_to_local_tenant.sh
To deploy the current state of the docker container to whatever tenant you last switched to, run:
docker-compose exec -u akvo akvo-flow ./dev-deploy.sh akvoflowsandbox $FLOW_GH_TOKEN
If you want to run both Flow and Flow Services locally and talking to each other, you will need add some config to your /etc/hosts:
127.0.0.1 services.akvoflow.local akvoflow.local
Then run:
docker-compose -f docker-compose.together.yml up --build -d
You will need to access Flow using the url http://akvoflow.local:8888/
Then read the Flow Services documentation for the Flow Services specific instructions.
The DNS alias is required because the UI is sending to Flow Services the baseUrl of the Flow service, which Flow Services needs to resolve to the Flow container. The way Docker works, this baseUrl cannot be "localhost", as "localhost" for the Flow Service container is itself. Adding a DNS entry allows for one level of indirection where "akvoflow.local" will be resolved to "127.0.0.1" for the Browser, while it resolves to the flow container for the flow-services container.
Once you have both flow and flow services running, if you are making changes to the Java report classes used in flow-services, you will need to run:
docker-compose exec -u akvo akvo-flow /bin/bash -c "cd GAE && mvn install"
To package and install the Flow jar in your local maven repository. Then you can use this Flow jar as a dependency in your local Flow Services dev environment. See Flow Services README for how to set it up.