aura issueshttps://gitlab.servus.at/aura/aura/-/issues2024-03-29T13:34:19+01:00https://gitlab.servus.at/aura/aura/-/issues/333Provide systemd service configs for AURA web/playout/recorder2024-03-29T13:34:19+01:00David TrattnigProvide systemd service configs for AURA web/playout/recorder- Store as `aura/config/aura-{compose-bundle}/aura-{compose-bundle}.service`
- Add info to https://docs.aura.radio/en/latest/administration/deployment-preparation.html#docker-engine-setup-in-production- Store as `aura/config/aura-{compose-bundle}/aura-{compose-bundle}.service`
- Add info to https://docs.aura.radio/en/latest/administration/deployment-preparation.html#docker-engine-setup-in-production1.0-alpha5https://gitlab.servus.at/aura/aura/-/issues/332Error when starting dashboard container during installation2024-03-28T20:39:34+01:00Martina Müllermartina@freirad.atError when starting dashboard container during installationI'm currently unable to install aura to a new server, which may be related to nginx.
## Steps to Reproduce
Installed alpha3 twice, once as sudo user, once as root.
Also installed alpha2 out of curiosity.
Both according to the relevant ...I'm currently unable to install aura to a new server, which may be related to nginx.
## Steps to Reproduce
Installed alpha3 twice, once as sudo user, once as root.
Also installed alpha2 out of curiosity.
Both according to the relevant docs.
At first I thought it might be a system issue but after reinstalling completely new and installing the alpha2 version (all unsuccessfully) I'm not sure about that.
## Actual Result
All installations failed at `docker compose up -d` / `make aura-web.up` when starting the containers.
All with the following message:
```
[+] Running 6/7
✔ Container dashboard-clock Started 14.6s
✔ Container steering-postgres Healthy 0.0s
✘ Container dashboard Error 104.6s
✔ Container tank-postgres Healthy 44.1s
✔ Container steering Healthy 46.6s
✔ Container tank Healthy 68.7s
⠏ Container aura-web-nginx-1 Created 93.9s
dependency failed to start: container dashboard is unhealthy
```
## Logs & configuration
logs of `dashboard`:
```
dashboard | awk: cmd. line:1: Unexpected token
dashboard | generated nginx-config
dashboard | server {
dashboard | listen 80;
dashboard | server_name ${AURA_HOST};
dashboard |
dashboard | location / {
dashboard | root /usr/share/nginx/html;
dashboard | index index.html;
dashboard | try_files $uri $uri/ /index.html;
dashboard | }
dashboard | }
dashboard | 2024/03/28 15:42:17 [notice] 395#395: using the "epoll" event method
dashboard | 2024/03/28 15:42:17 [notice] 395#395: nginx/1.24.0
dashboard | 2024/03/28 15:42:17 [notice] 395#395: built by gcc 12.2.1 20220924 (Alpine 12.2.1_git20220924-r4)
dashboard | 2024/03/28 15:42:17 [notice] 395#395: OS: Linux 6.1.0-18-amd64
dashboard | 2024/03/28 15:42:17 [notice] 395#395: getrlimit(RLIMIT_NOFILE): 1048576:1048576
dashboard | 2024/03/28 15:42:17 [notice] 395#395: start worker processes
dashboard | 2024/03/28 15:42:17 [notice] 395#395: start worker process 396
dashboard | 2024/03/28 15:42:17 [notice] 395#395: start worker process 397
dashboard | 2024/03/28 15:42:17 [notice] 395#395: start worker process 398
dashboard | 2024/03/28 15:42:17 [notice] 395#395: start worker process 399
dashboard | 2024/03/28 15:42:17 [notice] 395#395: start worker process 400
dashboard | 2024/03/28 15:42:17 [notice] 395#395: start worker process 401
dashboard | 2024/03/28 15:42:17 [notice] 395#395: start worker process 402
dashboard | 2024/03/28 15:42:17 [notice] 395#395: start worker process 403
```
In the `nginx` logs there was nothing written.
Only relevant changes to `.env` file. Everything else updated were the OIDC client ids and passwords, usernames, emails:
```
# Change to your custom domain name
AURA_HOST_NAME=aura-test.buero.freirad.at
# Set to http if you don't want to use TLS
AURA_HOST_PROTO=http
# Disable if you want to handle ssl yourself (e.g if you are deploying behind a reverse proxy)
AURA_HOST_CERTBOT_ENABLE=false
```
## Environment
Operating system: Debian 12
Permissions were all in order, no permission errors.
Installed on a completely fresh server.1.0-alpha4 — Raving Raccoon 🤪🦝Kay EffenbergerKay Effenbergerhttps://gitlab.servus.at/aura/aura/-/issues/328AURA Web: Review, rework and merge certain test configuration into relevant r...2024-03-19T14:49:33+01:00David TrattnigAURA Web: Review, rework and merge certain test configuration into relevant repositoriesParent: aura-tests#5+
---
Some hints can be found [here](https://gitlab.servus.at/aura/dashboard/-/blob/main/tests/docker-compose.yml?ref_type=heads#L20-39) and [there](https://gitlab.servus.at/aura/dashboard/-/blob/main/tests/docker-co...Parent: aura-tests#5+
---
Some hints can be found [here](https://gitlab.servus.at/aura/dashboard/-/blob/main/tests/docker-compose.yml?ref_type=heads#L20-39) and [there](https://gitlab.servus.at/aura/dashboard/-/blob/main/tests/docker-compose.yml?ref_type=heads#L48-107).
<mark>To be investigated and discussed by @kmohrf and @eigenwijsje</mark>
## Related
- aura-tests#3+1.0-alpha5Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/aura/-/issues/327aura-web: can't disable certbot2024-03-20T21:06:13+01:00Chris Pastlaura-web: can't disable certbotI ran aura-web using https and certbot before and needed to switch-back to http. So I commented out the relevant lines in the .env file - which are the default values:
```
# Change to your custom domain name
AURA_HOST_NAME=aura.fro.at
# ...I ran aura-web using https and certbot before and needed to switch-back to http. So I commented out the relevant lines in the .env file - which are the default values:
```
# Change to your custom domain name
AURA_HOST_NAME=aura.fro.at
# Set to http if you don't want to use TLS
# AURA_HOST_PROTO=http
# Disable if you want to handle ssl yourself (e.g if you are deploying behind a reverse proxy)
# AURA_HOST_CERTBOT_ENABLE=false
```
Since these changes had no effect, I removed all volumes at first - without success. So I hoped that `docker system prune -a` will fix the problem - but nginx started certbot again.
The only workaround was to either comment out the relevant lines in `config/services/nginx/run.sh` or to override the relevant line in `config/aura-web/docker-compose.yml`.
```
nginx-1 | 2024-03-18T18:52:50.710415965Z generated nginx-config
nginx-1 | 2024-03-18T18:52:50.710446943Z Running Certbot
nginx-1 | 2024-03-18T18:52:50.921482399Z Saving debug log to /var/log/letsencrypt/letsencrypt.log
nginx-1 | 2024-03-18T18:52:51.992607388Z Unable to register an account with ACME server. The ACME server believes admin@example.com is an invalid email address. Please ensure it is a valid email and attempt registration again.
nginx-1 | 2024-03-18T18:52:51.992632295Z Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
```1.0-alpha4 — Raving Raccoon 🤪🦝Kay EffenbergerKay Effenbergerhttps://gitlab.servus.at/aura/aura/-/issues/326Running aura-web behind a reverse proxy with HTTP(S) port forwarding2024-03-20T21:05:02+01:00Chris PastlRunning aura-web behind a reverse proxy with HTTP(S) port forwardingWe need to run `aura-web` behind a reverse proxy with port forwarding and -translation; meaning requests to `https://aura.fro.at:8443` will be forwarded to the internal host running aura-web on port 80.
While the dashboard login page ca...We need to run `aura-web` behind a reverse proxy with port forwarding and -translation; meaning requests to `https://aura.fro.at:8443` will be forwarded to the internal host running aura-web on port 80.
While the dashboard login page can be reached via this url from the internet, nothing happens when the "Anmelden" button is pressed. Since I ran into related problems while testing, I assumed an issue regarding the callback URLs. So changed these envars in the config - but without success yet:
```
AURA_TANK_CALLBACK_BASE_URL=https://aura.fro.at:8443
AURA_DASHBOARD_CALLBACK_BASE_URL=https://aura.fro.at:8443
```
(It's btw not clear to me if these settings are reflected immediately after restarting aura-web)
Is there a way to fix this?1.0-alpha4 — Raving Raccoon 🤪🦝https://gitlab.servus.at/aura/aura/-/issues/324Move Dashboard integration tests to dedicated `aura-tests` repository2024-03-11T23:09:46+01:00David TrattnigMove Dashboard integration tests to dedicated `aura-tests` repositoryParent: aura#175+
---
- provide a `make test` target.
- provide a `make coverage` target, if applicable
- Provide a basic CI/CD pipeline with logic from the one in Dashboard.Parent: aura#175+
---
- provide a `make test` target.
- provide a `make coverage` target, if applicable
- Provide a basic CI/CD pipeline with logic from the one in Dashboard.1.0-alpha5Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/aura/-/issues/323Test AURA Docker Compose Deployment using Vagrant in CI/CD Pipeline2024-03-11T23:09:00+01:00David TrattnigTest AURA Docker Compose Deployment using Vagrant in CI/CD PipelineParent: https://gitlab.servus.at/aura/aura/-/issues/175+
---
This could replace our manual installation tests before releasing.Parent: https://gitlab.servus.at/aura/aura/-/issues/175+
---
This could replace our manual installation tests before releasing.1.0-alpha5Ole Binderole@freirad.atOle Binderole@freirad.athttps://gitlab.servus.at/aura/aura/-/issues/322Add CLI command to completly erase AURA2024-03-07T12:03:57+01:00David TrattnigAdd CLI command to completly erase AURAThis comes in handy, since people often struggle re-installing AURA on top of a previous installations and are not aware how to get rid of old artifacts. Since this is a quite dangerous operation there is a confirmation dialog required.This comes in handy, since people often struggle re-installing AURA on top of a previous installations and are not aware how to get rid of old artifacts. Since this is a quite dangerous operation there is a confirmation dialog required.1.0-alpha7David TrattnigDavid Trattnighttps://gitlab.servus.at/aura/aura/-/issues/321Error while calling `make aura-web.update` on a version branch2024-03-06T16:43:41+01:00David TrattnigError while calling `make aura-web.update` on a version branch```bash
stefan@desktop:/opt/aura$ make aura-web.update
make: poetry: Datei oder Verzeichnis nicht gefunden
make: poetry: Datei oder Verzeichnis nicht gefunden
git pull
Im Moment auf keinem Branch.
Bitte geben Sie den Branch an, welchen S...```bash
stefan@desktop:/opt/aura$ make aura-web.update
make: poetry: Datei oder Verzeichnis nicht gefunden
make: poetry: Datei oder Verzeichnis nicht gefunden
git pull
Im Moment auf keinem Branch.
Bitte geben Sie den Branch an, welchen Sie zusammenführen möchten.
Siehe git-pull(1) für weitere Details.
git pull <Remote-Repository> <Branch>
make: *** [Makefile:131: aura-web.update] Fehler 1
```
## Steps to Reproduce
1. Checkout a branch e.g `1.0.0-alpha3`
2. The branch is in detached state
3. Call `make aura-web.update`
## Expected Result
- Git cannot be pulled, as the branch is in detached state. Therefore this is by-passed.
- Instead the branch should be re-cloned, because it could possibly be changed due to a hotfix.
- `docker compose pull` is called correctly.
## Actual Result
- Git cannot be pulled, as the branch is in detached state. An error is raised.
- `docker compose pull` is not called because of the previous command failing.1.0-alpha5https://gitlab.servus.at/aura/aura/-/issues/320Error "make: poetry: File or directory not found" when calling "make aura-web...2024-03-06T16:49:14+01:00David TrattnigError "make: poetry: File or directory not found" when calling "make aura-web.init"```bash
stefan@desktop:/opt/aura$ make aura-web.init
make: poetry: Datei oder Verzeichnis nicht gefunden
make: poetry: Datei oder Verzeichnis nicht gefunden
sudo chown -R stefan:stefan /opt/aura
sudo mkdir -p \
```
## Steps to Reproduce...```bash
stefan@desktop:/opt/aura$ make aura-web.init
make: poetry: Datei oder Verzeichnis nicht gefunden
make: poetry: Datei oder Verzeichnis nicht gefunden
sudo chown -R stefan:stefan /opt/aura
sudo mkdir -p \
```
## Steps to Reproduce
1. Call `make aura-web.init` as per docs
2. Error displayed `make: poetry: Datei oder Verzeichnis nicht gefunden`
3. Target still proceeds with other commands
## Expected Result
- Target proceeds with all commands and no error
## Actual Result
- Error displayed `make: poetry: Datei oder Verzeichnis nicht gefunden`
- Target still proceeds with other commands
## Logs & configuration
<details><summary>Click to expand</summary>
```bash
stefan@desktop:/opt/aura$ make aura-web.init
make: poetry: Datei oder Verzeichnis nicht gefunden
make: poetry: Datei oder Verzeichnis nicht gefunden
sudo chown -R stefan:stefan /opt/aura
sudo mkdir -p \
/opt/aura/audio/source \
/opt/aura/audio/import \
/opt/aura/audio/playlist \
/opt/aura/logs/
sudo chown -R stefan:2872 \
/opt/aura/audio/source \
/opt/aura/audio/import \
/opt/aura/audio/playlist \
/opt/aura/logs/
sudo chmod -R g+rw \
/opt/aura/audio/source \
/opt/aura/audio/import \
/opt/aura/audio/playlist \
/opt/aura/logs/
Now '/opt/aura' feels like home.
sudo mkdir -p \
/opt/aura/logs/tank \
/opt/aura/logs/nginx \
/opt/aura/logs/letsencrypt
sudo chown -R stefan:2872 \
/opt/aura/logs/tank
sudo chmod -R g+rw \
/opt/aura/logs/tank
sudo chown -R 101:2872 \
/opt/aura/logs/letsencrypt \
/opt/aura/logs/nginx
cp -n config/aura-web/sample.env config/aura-web/.env
```
</details>
## Environment
- aura alpha-3
- Debian 11
- Bash1.0-alpha5https://gitlab.servus.at/aura/aura/-/issues/318Demo Server Configuration2024-03-05T11:33:42+01:00David TrattnigDemo Server Configuration- Clear DB: Remove all RH data from database
- Create superuser accounts for team
- Create demo accounts for public use:
- `demo_pm`: Programme Manager Role
- `demo_host`: Host Role- Clear DB: Remove all RH data from database
- Create superuser accounts for team
- Create demo accounts for public use:
- `demo_pm`: Programme Manager Role
- `demo_host`: Host Role1.0-alpha5https://gitlab.servus.at/aura/aura/-/issues/317DockerHub Tag `latest` should refer to the latest release, not the latest (un...2024-03-18T22:29:24+01:00David TrattnigDockerHub Tag `latest` should refer to the latest release, not the latest (unstable) main version1.0-alpha4 — Raving Raccoon 🤪🦝Kay EffenbergerKay Effenbergerhttps://gitlab.servus.at/aura/aura/-/issues/315Docs: Add infos on Radio Station Administration2024-03-08T11:24:06+01:00David TrattnigDocs: Add infos on Radio Station AdministrationParent: https://gitlab.servus.at/aura/aura/-/issues/221+
---Parent: https://gitlab.servus.at/aura/aura/-/issues/221+
---1.0-alpha4 — Raving Raccoon 🤪🦝David TrattnigDavid Trattnighttps://gitlab.servus.at/aura/aura/-/issues/314When calling `aura-web.init` or `aura-playout.init`, render warning when ther...2024-02-26T14:12:50+01:00David TrattnigWhen calling `aura-web.init` or `aura-playout.init`, render warning when there is an existing Docker Compose `.env` file- Inform to review the config file structure
- Possible add ability to pass an argument to override existing config (esp. for CI/CD usage)- Inform to review the config file structure
- Possible add ability to pass an argument to override existing config (esp. for CI/CD usage)1.0-alpha7David TrattnigDavid Trattnighttps://gitlab.servus.at/aura/aura/-/issues/313Remove the need for a trailing slash when configuring the AURA Playout Base URLs2024-02-26T11:20:05+01:00David TrattnigRemove the need for a trailing slash when configuring the AURA Playout Base URLsA trailing slash should be not mandatory, as it creates chances for misconfiguration.
See [base URLs configuration in the docs](https://docs.aura.radio/en/latest/administration/aura-playout.html#update-the-configuration-file).A trailing slash should be not mandatory, as it creates chances for misconfiguration.
See [base URLs configuration in the docs](https://docs.aura.radio/en/latest/administration/aura-playout.html#update-the-configuration-file).1.0-alpha5https://gitlab.servus.at/aura/aura/-/issues/312[EPIC] Simplify Architecture: Clock data retrieval from Engine API and Steering2024-03-21T18:54:33+01:00David Trattnig[EPIC] Simplify Architecture: Clock data retrieval from Engine API and SteeringAfter #176+ is implemented, we have the chance to simplify the logic for the Studio Clock drastically.
This affects:
- `engine`: Remove `clock.py` and related logic
- `engine-api`: remove the clock endpoint
- `dashboard-clock`: Refactor...After #176+ is implemented, we have the chance to simplify the logic for the Studio Clock drastically.
This affects:
- `engine`: Remove `clock.py` and related logic
- `engine-api`: remove the clock endpoint
- `dashboard-clock`: Refactor to retrieve data from `engine-api` and `steering`. Depending how we solve the playlist storage this could or could not involve `tank`.
## Dependencies
- #176+1.0-alpha8https://gitlab.servus.at/aura/aura/-/issues/311Add month view to calendar2024-02-23T17:00:42+01:00David TrattnigAdd month view to calendarAdd a "month view" of the calendar along with the "week view" and "day view".Add a "month view" of the calendar along with the "week view" and "day view".1.2https://gitlab.servus.at/aura/aura/-/issues/310Change `aura` UID:GID to some value in the sysuser range2024-03-27T10:34:51+01:00David TrattnigChange `aura` UID:GID to some value in the sysuser rangeThe target `make aura-user.add` now emits this warning:
```shell
useradd warning: aura's uid 2872 is greater than SYS_UID_MAX 999
```
Let's discuss and see if we can use a valid and conflict UID:GID in the sysuser range.The target `make aura-user.add` now emits this warning:
```shell
useradd warning: aura's uid 2872 is greater than SYS_UID_MAX 999
```
Let's discuss and see if we can use a valid and conflict UID:GID in the sysuser range.1.0-alpha4 — Raving Raccoon 🤪🦝Martina Müllermartina@freirad.atMartina Müllermartina@freirad.athttps://gitlab.servus.at/aura/aura/-/issues/309Encapsulate some relevant AURA Playout commands as make targets2024-03-21T18:07:23+01:00David TrattnigEncapsulate some relevant AURA Playout commands as make targets- To check if PipeWire is running run `ps -fp $(pgrep -d, -x pipewire)`.
- List auto-connect ports `docker compose run engine-core wpexec /etc/wireplumber/scripts/ls-ports.lua`
- `docker compose up -d`
- `docker compose down`- To check if PipeWire is running run `ps -fp $(pgrep -d, -x pipewire)`.
- List auto-connect ports `docker compose run engine-core wpexec /etc/wireplumber/scripts/ls-ports.lua`
- `docker compose up -d`
- `docker compose down`1.0-alpha6David TrattnigDavid Trattnighttps://gitlab.servus.at/aura/aura/-/issues/306Docs: Add basic info on studio clock2024-03-21T18:07:43+01:00David TrattnigDocs: Add basic info on studio clock1.0-alpha7David TrattnigDavid Trattnig