dashboard merge requestshttps://gitlab.servus.at/aura/dashboard/-/merge_requests2024-02-28T23:14:27+01:00https://gitlab.servus.at/aura/dashboard/-/merge_requests/40fix: add before_script stage for ci2024-02-28T23:14:27+01:00Chris Pastlfix: add before_script stage for ci1.0-alpha3 — Playful Platypus ▶️🦦Chris PastlChris Pastlhttps://gitlab.servus.at/aura/dashboard/-/merge_requests/39Fix docker image names for release2024-02-28T22:53:36+01:00Chris PastlFix docker image names for releaseThis reverts commit 4a587f8f3e9e3642db1666b0e1bae37355f26b2e and renames the pushed image to 'main' instead of 'unstable' again. As discussed in matrix.This reverts commit 4a587f8f3e9e3642db1666b0e1bae37355f26b2e and renames the pushed image to 'main' instead of 'unstable' again. As discussed in matrix.1.0-alpha3 — Playful Platypus ▶️🦦Chris PastlChris Pastlhttps://gitlab.servus.at/aura/dashboard/-/merge_requests/13FEAT(gitlab-ci):Push from Feature Branch2023-06-07T22:24:10+02:00Kay EffenbergerFEAT(gitlab-ci):Push from Feature BranchIf a Merge Request on a feature Branch is created, the Image will pushed to gitlab registryIf a Merge Request on a feature Branch is created, the Image will pushed to gitlab registry1.0-alpha2 — ⚖️🐦 Precise PheasantDavid TrattnigDavid Trattnighttps://gitlab.servus.at/aura/dashboard/-/merge_requests/3Show duration of playlists2020-08-25T15:38:27+02:00Richard BlechingerShow duration of playlistsAs described in #40, this PR adds the total duration of a playlist to every relevant spot in the dashboard, and pre-warns the user if the playlist they select for a given timeslot is too long/too short.
![CleanShot_2020-08-25_at_13.42.4...As described in #40, this PR adds the total duration of a playlist to every relevant spot in the dashboard, and pre-warns the user if the playlist they select for a given timeslot is too long/too short.
![CleanShot_2020-08-25_at_13.42.41](/uploads/444f7c14c92c75cfd71afba421a5c591/CleanShot_2020-08-25_at_13.42.41.png)
![CleanShot_2020-08-25_at_13.42.49](/uploads/69103ac7ca1a1d6c9a9fb4033b7629d4/CleanShot_2020-08-25_at_13.42.49.png)
![CleanShot_2020-08-25_at_13.43.07](/uploads/62011b2a45e4647410aad376dd8f7df3/CleanShot_2020-08-25_at_13.43.07.png)
![CleanShot_2020-08-25_at_13.43.16](/uploads/aee067b9a30d74ba7aec16a744da8d4f/CleanShot_2020-08-25_at_13.43.16.png)
![CleanShot_2020-08-25_at_13.43.23](/uploads/828e017639b730c585d1b7d50865602e/CleanShot_2020-08-25_at_13.43.23.png)1.0-alpha2 — ⚖️🐦 Precise Pheasanthttps://gitlab.servus.at/aura/dashboard/-/merge_requests/1Add expandable block for show schedules to ShowManager2020-08-25T15:58:10+02:00Richard BlechingerAdd expandable block for show schedules to ShowManagerAs described in #43, this PR adds a schedule block to the show manager that shows the configured schedules for a show. Should there be more than two, it becomes an expandable block that can be shown/hidden at the users convenience.
Demo...As described in #43, this PR adds a schedule block to the show manager that shows the configured schedules for a show. Should there be more than two, it becomes an expandable block that can be shown/hidden at the users convenience.
Demonstration/screenshot seen below
![CleanShot_2020-08-24_at_15.01.28](/uploads/055dae166c01350187a25dc968b395b2/CleanShot_2020-08-24_at_15.01.28.mp4)
![CleanShot_2020-08-24_at_15.03.12](/uploads/6f683afcae659540d8db003d6931fc2e/CleanShot_2020-08-24_at_15.03.12.png)1.0-alpha2 — ⚖️🐦 Precise Pheasanthttps://gitlab.servus.at/aura/dashboard/-/merge_requests/8Develop2022-01-14T10:46:23+01:00David TrattnigDevelopPlease review and merge to masterPlease review and merge to masterAura 0.9Richard BlechingerRichard Blechingerhttps://gitlab.servus.at/aura/dashboard/-/merge_requests/7Changed fallback id to default playlist id. #772021-07-30T10:42:37+02:00David TrattnigChanged fallback id to default playlist id. #77@pretzelhands I've already changed the fields, because I needed it to implement engine#52
Please review if I didn't miss anything and merge if things are fine :-)@pretzelhands I've already changed the fields, because I needed it to implement engine#52
Please review if I didn't miss anything and merge if things are fine :-)Aura 0.9Richard BlechingerRichard Blechingerhttps://gitlab.servus.at/aura/dashboard/-/merge_requests/41feat: add gitlab issue templates2024-03-08T10:27:33+01:00David Trattnigfeat: add gitlab issue templatesSee https://gitlab.servus.at/aura/aura/-/issues/319+See https://gitlab.servus.at/aura/aura/-/issues/319+David TrattnigDavid Trattnighttps://gitlab.servus.at/aura/dashboard/-/merge_requests/38refactor(DOCKER): Use main tag and main-commit-sha for pushing to docker hub2024-02-06T11:48:07+01:00Kay Effenbergerrefactor(DOCKER): Use main tag and main-commit-sha for pushing to docker hubhttps://gitlab.servus.at/aura/aura/-/issues/149https://gitlab.servus.at/aura/aura/-/issues/149Kay EffenbergerKay Effenbergerhttps://gitlab.servus.at/aura/dashboard/-/merge_requests/15Feat rennovate2023-09-01T14:47:12+02:00Kay EffenbergerFeat rennovateAdds Renovate Bot for dependency UpdatesAdds Renovate Bot for dependency UpdatesKay EffenbergerKay Effenbergerhttps://gitlab.servus.at/aura/dashboard/-/merge_requests/14ADD: nginx Dockerfile2023-08-25T11:40:07+02:00Kay EffenbergerADD: nginx DockerfileAdd nginx-unpriviliegd-certbot Dockerfile and build it via gitlab-ciAdd nginx-unpriviliegd-certbot Dockerfile and build it via gitlab-cihttps://gitlab.servus.at/aura/dashboard/-/merge_requests/12feat(nginx): deploy dashboard standalone2022-08-11T11:36:49+02:00EorlBruderfeat(nginx): deploy dashboard standaloneNginx in the Docker-container now ONLY deploys dashboard on port 80. All configs related to other services will be moved to a separate container. Certbot has been removed from the Dockerfile.
Fixes #105
Added as draft, since merging w...Nginx in the Docker-container now ONLY deploys dashboard on port 80. All configs related to other services will be moved to a separate container. Certbot has been removed from the Dockerfile.
Fixes #105
Added as draft, since merging will break the docker-compose setup in AURA/meta for now, so we first need to make corresponding changes there.EorlBruderEorlBruderhttps://gitlab.servus.at/aura/dashboard/-/merge_requests/11Fix error code handling for scheduling API2022-05-04T10:15:32+02:00Konrad MohrfeldtFix error code handling for scheduling APIThis MR makes the appropriate adjustments to handle the changes from the aura/steering!22 merge request, namely the renamed attribute names in scheduling requests and the HTTP 409 status codes sent for schedule conflict responses.
This ...This MR makes the appropriate adjustments to handle the changes from the aura/steering!22 merge request, namely the renamed attribute names in scheduling requests and the HTTP 409 status codes sent for schedule conflict responses.
This MR is based on !9 and !10 which should be merged before.
Fixes #93.https://gitlab.servus.at/aura/dashboard/-/merge_requests/10Allow API store consumers to use traditional flow-control2022-05-04T10:14:45+02:00Konrad MohrfeldtAllow API store consumers to use traditional flow-controlThis MR implements a solution that helps us to gradually migrate away from the callback-pattern used in the API store methods.
I’ve stumbled on this while looking for ways to solve #93, because the current callback-approach makes it qui...This MR implements a solution that helps us to gradually migrate away from the callback-pattern used in the API store methods.
I’ve stumbled on this while looking for ways to solve #93, because the current callback-approach makes it quite hard to implement proper error handling in the view handlers that are calling the store methods.
Basically it allows us to refactor a function like this:
```js
submitSchedule(ctx, data) {
ctx.commit('loading', 'schedules')
let uri = process.env.VUE_APP_API_STEERING_SHOWS + data.showId + '/schedules/'
axios.post(uri, data.schedule, {
withCredentials: true,
headers: {'Authorization': 'Bearer ' + ctx.rootState.auth.user.access_token}
}).then(response => {
ctx.commit('finishLoading', 'schedules')
if (data && typeof (data.callback) === 'function') {
data.callback(response)
}
}).catch(error => {
handleApiError(this, error, 'could not load timeslots')
if (data && typeof (data.callbackCancel) === 'function') {
data.callbackCancel()
}
})
}
```
into this:
```js
submitSchedule(ctx, data) {
ctx.commit('loading', 'schedules')
let uri = process.env.VUE_APP_API_STEERING_SHOWS + data.showId + '/schedules/'
return axios.post(uri, data.schedule, {
withCredentials: true,
headers: {'Authorization': 'Bearer ' + ctx.rootState.auth.user.access_token}
}).then(response => {
ctx.commit('finishLoading', 'schedules')
return callOrReturn(response, data?.callback)
}).catch(error => {
APIError.handle(error, 'Unable to submit schedule', data, this)
})
}
```
Whether or not callbacks are called is based on the caller of the function by either passing callbacks or not. If callbacks are provided we assume that the caller relies on them to handle the response data. If they are not provided we assume that the caller wants to handle Promise objects. This is tangentially related to #55, though strictly speaking this change is more about enabling the caller to properly handle errors than it is about the specific syntax used.
More details on the implementation and motivation can be found in 180ba9392f7abb79d7a6f667ecccaf4894b144a9.
This MR is based on !9 which should be merged before.https://gitlab.servus.at/aura/dashboard/-/merge_requests/9Update toolchain and cleanup code2022-05-04T10:16:23+02:00Konrad MohrfeldtUpdate toolchain and cleanup codeThis MR updates the build toolchain to Vue CLI 5 and Tailwind 3.x, cleanes up some code, and removes some unused libraries.
Upgrading the toolchain wasn’t really my intention at first, but the linter complained about a lot of code when ...This MR updates the build toolchain to Vue CLI 5 and Tailwind 3.x, cleanes up some code, and removes some unused libraries.
Upgrading the toolchain wasn’t really my intention at first, but the linter complained about a lot of code when I started the dev server. Auto-formatting the code caused some very weird issues though, like completely unindented HTML in some places. Instead of trying to find a fix for these issues with the old tooling I figured that we’d be better off with the using the updated tooling and fix things from there. Fortunately most problems were fixed by the migration.
I’ve noticed that there are still quite a few issues after applying the linting configuration, so I’ve opened #95.https://gitlab.servus.at/aura/dashboard/-/merge_requests/5Feature/timeslot table2020-09-14T15:34:18+02:00Richard BlechingerFeature/timeslot tableCloses #34Closes #34https://gitlab.servus.at/aura/dashboard/-/merge_requests/4Meta validation for Website and Email2020-09-14T15:34:12+02:00Richard BlechingerMeta validation for Website and EmailCloses #27Closes #27https://gitlab.servus.at/aura/dashboard/-/merge_requests/2Bugfix: Auth on reload2020-08-26T13:51:48+02:00Richard BlechingerBugfix: Auth on reloadWhen reloading the dashboard on any page that is not 'Home', the auth process would fail to run fast enough to be done by the the time when the ShowManager/FileManager start requesting resources
This bugfix wraps the show fetching mecha...When reloading the dashboard on any page that is not 'Home', the auth process would fail to run fast enough to be done by the the time when the ShowManager/FileManager start requesting resources
This bugfix wraps the show fetching mechanism in a watcher to ensure that we have an auth result before any further requests go out. Thus you can safely reload the dashboard on any page.