-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
0 parents
commit b510d51
Showing
1 changed file
with
18 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
# Private Windmill Hub | ||
|
||
## Setup | ||
|
||
- Fill in the `.env` file with your desired database password, the url of your Windmill instance and your license key. | ||
- Run `docker-compose up -d` to start the hub and database. | ||
|
||
You can enable HTTPS handling by Caddy by adding the 443 port to the Caddy service in the docker-compose.yml file. | ||
|
||
Authentication on the Hub is done through the Windmill instance. Both the Hub and the Windmill instances need to be running on the same domain for the authentication to work. | ||
For instance, if the Windmill instance is available on `windmill.example.com`, the Hub should be accessible on a similar subdomain like `hub.example.com`. You will also need to set `COOKIE_DOMAIN` in the .env file of the Windmill instance (server container) to the root domain (e.g. `example.com`). | ||
|
||
## Usage | ||
|
||
As described above, logging in on the hub will redirect you to the Windmill instance you specified in the `.env` file. | ||
Superadmins of the Windmill instance can approve resource types, scripts, flows, and apps on the Hub. | ||
Only approved content will be available to users on the Windmill instance. | ||
|