Skip to content

Default web frontend, enabling browsing the Alkemio platform - so the hosted Challenges and communities collaborating around those Challenges.

License

Notifications You must be signed in to change notification settings

alkem-io/client-web

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Alkemio Logo

Empowering society. The platform to succeed in working on challenges, together.

Build & Deploy to Dev Coverage Status Crowdin

Alkemio Web Client

Welcome to the Alkemio web client - allowing you to browse the contents of the Alkemio Platform. Please see the Alkemio repository for more details on the Alkemio platform.

This client is based on React, and is intended to showcase how clients in general can interact with the domain model exposed by the Alkemio server.

Configuration

Beyond the bootstrap configuration to point to the Alkemio server, all further configuration is obtained from the server configuration graphql schema.

Launching the client

To develop with the client, it is necessary to leverage the Alkemio server repository to get get a working instance of the Alkemio server running. For details on getting a working Alkemio server running please consult the following documentation.

Once you can confirm that you have a running Alkemio server, then you can start with the launching of the Alkemio client.

In the project directory, you can run:

  • npm install
  • npm start

This runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

NB: The alkemio web client runs on the port specified by the PORT env variable (3001 by default). All the alkemio dependencies run behind a traefik reverse proxy running on port 3000. Manually navigate to http://localhost:3000 to open the app.

The page will reload if you make edits.
By default, eslint will cause compilation errors and be prominently visible. Setting ESLINT_NO_DEV_ERRORS=true in .env.local reduces eslint errors to warnings in the console.

Environment variables

Environment variables are used as usual in React applications.

Vite does not acknowledge variable at runtime, so ./.build/docker/env.sh is run everytime before launching the application. For it to work properly, you need to have a .env file in the root of the project. Yes - it is commited to the code base. Locally you can use .env.local.

The script is reading the variables from .env and combines them with the values from the same variables in your deployment environment. The result is added to ./.build/docker/.env.base. The variables are also attached to the window object of the browser, via _env_ field.

Development stack

The client development stack includes:

For Typescript, the Javascript generated is ES2016.

Supported web browsers

The Javascript generated is ES2016, which is widely supported.

In addition the client looks to support the primary web browsers active in the market i.e. Edge, Chrome, Mozilla etc. Details of what versions are supported are in the package.json file.

Docker

The repo is also set up to generate a Docker image.

  • To create the docker image: docker build -t alkemio/client-web:[tag] where [tag] can be any value
  • To add build arguments - docker build --build-arg [argument]=[value]
    • Argument can be the following: ARG_GRAPHQL_ENDPOINT
  • To run a container based on the image: docker container run -p 80:80 alkemio/client-web:[tag] and then navigate with a browser to http://localhost:80

Pushing code the dockerspace

We have automated the creation and deployment of containers to docker space via a github action. To automaticly trigger the build up to dockerspace the following steps should be taken:

  • Ensure that the code that you would like to create the container from is pushed / merged into the develop branch.
  • Create a github release and tag it with the appropriate version number ie. v0.1.3
  • Go to github actions and view the push to docker action to see if everything ran correctly.

Testing

Tools

  • VS Code - development environment
  • Jest - component testing

Test levels

  • Component tests - testing each component in isolation
    • Run tests with coverage npm run-script test:coverage
  • UI E2E tests - test are part of this repository

About

Default web frontend, enabling browsing the Alkemio platform - so the hosted Challenges and communities collaborating around those Challenges.

Topics

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Packages

No packages published

Languages