- Explore all missions across your organizations by products
- Identify care missions like days off, sick days and team building events
- Daily track your time by mission
- Track throughout the year who worked on same missions with you
- Let your coworkers know when you will not be available
Asa runs on Poja. It's the best way we know to host Spring Boot applications. Within a few clicks, you have your Spring Boot running with a publicly accessible URL, and with your CI/CD pipelines automatically configured on Github.
First, set all following environment variables:
ASA_LOGOUT_URL=
AWS_SES_SOURCE=
CASDOOR_LOGOUT_URL=
SERVER_ERROR_INCLUDEMESSAGE=
SPRING_DATASOURCE_PASSWORD=
SPRING_DATASOURCE_URL=
SPRING_DATASOURCE_USERNAME=
SPRING_FLYWAY_OUTOFORDER=
SPRING_SECURITY_OAUTH2_CLIENT_PROVIDER_CASDOOR_ISSUERURI=
SPRING_SECURITY_OAUTH2_CLIENT_PROVIDER_CASDOOR_USERNAMEATTRIBUTE=
SPRING_SECURITY_OAUTH2_CLIENT_REDIRECTURI=
SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_CASDOOR_CLIENTID=
SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_CASDOOR_CLIENTSECRET=
SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_CASDOOR_SCOPE_0_=
SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_CASDOOR_SCOPE_1_=
SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_CASDOOR_SCOPE_2_=
ASA_CARE_PRODUCT_CODE=
ASA_PAID_CARE_MISSION_CODES=
SENSITIVE_WORKERS_CODES=
MAX_LATENESS_REPORT=
Then, run Spring Boot as usual,
for example by building an uber jar through gradle bootJar,
then by launching java -jar asa.jar
(here is an Uber Jar we built: v1).
As there are a lot of environment variables to set,
you probably want to load them through an .env file:
export $(cat .env | xargs) && java -jar asa.jar.
Last, visit http://localhost:8080