* ci: push dev images to ghcr Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * *: use new ghcr images Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * website/docs: use ghcr proxy Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org>
		
			
				
	
	
	
		
			1.5 KiB
		
	
	
	
	
	
	
	
			
		
		
	
	title
| title | 
|---|
| Frontend-only development environment | 
If you want to only make changes on the UI, you don't need a backend running from source. You can user the docker-compose install with a few customizations.
Prerequisites
- Node (any recent version should work, we use 16.x to build)
 - Make (again, any recent version should work)
 - Docker and docker-compose
 
Instructions
- 
Clone the git repo from https://github.com/goauthentik/authentik
 - 
In the cloned repository, follow the docker-compose installation instructions here
 - 
Add the following entry to your
.envfile:AUTHENTIK_IMAGE=goauthentik.io/dev-server AUTHENTIK_TAG=gh-next AUTHENTIK_OUTPOSTS__DOCKER_IMAGE_BASE=goauthentik.io/dev-%(type)s:gh-next AUTHENTIK_LOG_LEVEL=debug AUTHENTIK_WEB_LOAD_LOCAL_FILES=trueThis will cause authentik to use the beta images.
 - 
Add this volume mapping to your compose file
version: '3.2' services: # [...] server: # [...] volumes: - ./web:/web - ./local.env.yml:/local.env.ymlThis makes the local web files and the config file available to the authentik server.
 - 
Run
docker-compose up -dto apply those changes to your containers. - 
cd web - 
Run
npm iand thennpm run watchto start the build process. 
You can now access authentik on http://localhost:9000 (or https://localhost:9443).
You might also want to complete the initial setup under /if/flow/initial-setup/.