Not entirely done yet, but almost there. You can already authorize any RS apps against your local account (username@localhost:3000).
How to run/test
There are instructions in the README for adding a bucket to Minio. The LC Dockerfile is available in this branch, so you can also use build instead of image to build LC locally from that: 5apps/liquor-cabinet#2
To do
Create Web App model, integrate Manifique for fetching app metadata and icons
Add admin page for inspecting indexed Web Apps
Add Docker Compose services for S3 (Minio) and Liquor Cabinet (RS API)
Only use the primary domain/ou for RS (except for the user address in dev)
Fix bug in Liquor Cabinet signature generation (fails in the new LC Docker container for some reason)
Finish storage dashboard (add more info to auths, allow revocation)
Not entirely done yet, but almost there. You can already authorize any RS apps against your local account (`username@localhost:3000`).
### How to run/test
There are instructions in the README for adding a bucket to Minio. The LC Dockerfile is available in this branch, so you can also use `build` instead of `image` to build LC locally from that: https://gitea.kosmos.org/5apps/liquor-cabinet/pulls/2
### To do
* [x] Create Web App model, integrate Manifique for fetching app metadata and icons
* [x] Add admin page for inspecting indexed Web Apps
* [x] Add Docker Compose services for S3 (Minio) and Liquor Cabinet (RS API)
* [x] Only use the primary domain/ou for RS (except for the user address in dev)
* [x] Fix bug in Liquor Cabinet signature generation (fails in the new LC Docker container for some reason)
* [x] Finish storage dashboard (add more info to auths, allow revocation)
* [x] Add missing specs (mostly just Web App related)
closes #94
closes #142
@galfert I actually get the same signature issue we talked about when running Liquor Cabinet on the host directly. Going to forgo further debugging in favor of 5apps/liquor-cabinet#3
@galfert I actually get the same signature issue we talked about when running Liquor Cabinet on the host directly. Going to forgo further debugging in favor of https://gitea.kosmos.org/5apps/liquor-cabinet/issues/3
Update: Liquor Cabinet now works (without any changes) with Docker Compose, and also supports v4 signatures now. So the RS integration now works entirely in dev and should also be compatible with Garage.
Update: Liquor Cabinet now works (without any changes) with Docker Compose, and also supports v4 signatures now. So the RS integration now works entirely in dev and should also be compatible with Garage.
Respect start_url from Web App Manifest when launching apps from the Storage dashboard
Add (configurable) notifications for new authorizations
More updates:
* Respect `start_url` from Web App Manifest when launching apps from the Storage dashboard
* Add (configurable) notifications for new authorizations
galfert
approved these changes 2023-12-05 03:58:04 +00:00
When running docker compose up, I get the following error from the accounts-ldap-1 instance:
ERR - createprlistensockets - PR_Bind() on address conversion failed file /data/run/slapd-localhost.socket failed: Netscape Portable Runtime error -5968 (TCP-specific function attempted on a non-TCP file descriptor.)
I deleted all my old containers and images, but that didn't help.
Changes look all good. Great job 🙌
So far I wasn't able to test it though.
When running `docker compose up`, I get the following error from the `accounts-ldap-1` instance:
```
ERR - createprlistensockets - PR_Bind() on address conversion failed file /data/run/slapd-localhost.socket failed: Netscape Portable Runtime error -5968 (TCP-specific function attempted on a non-TCP file descriptor.)
```
I deleted all my old containers and images, but that didn't help.
Maybe it might be nice to also link the name or the client_id field directly to the launch URL? Just to easier open the app without having to go via the dropdown.
Maybe it might be nice to also link the name or the client_id field directly to the launch URL? Just to easier open the app without having to go via the dropdown.
When running docker compose up, I get the following error from the accounts-ldap-1 instance:
If you want to start with a fresh LDAP container (or Rails, after switching from running it on the host), you also have to delete the files in ./tmp first.
However, if the documented quick start commands are not working on a fresh repo checkout, please file an issue for that, and I'll check it out asap!
> When running docker compose up, I get the following error from the accounts-ldap-1 instance:
If you want to start with a fresh LDAP container (or Rails, after switching from running it on the host), you also have to delete the files in `./tmp` first.
However, if the documented quick start commands are not working on a fresh repo checkout, please file an issue for that, and I'll check it out asap!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Not entirely done yet, but almost there. You can already authorize any RS apps against your local account (
username@localhost:3000).How to run/test
There are instructions in the README for adding a bucket to Minio. The LC Dockerfile is available in this branch, so you can also use
buildinstead ofimageto build LC locally from that: 5apps/liquor-cabinet#2To do
closes #94
closes #142
@galfert I actually get the same signature issue we talked about when running Liquor Cabinet on the host directly. Going to forgo further debugging in favor of 5apps/liquor-cabinet#3
157d7efeb6to1995e6dda2Update: Liquor Cabinet now works (without any changes) with Docker Compose, and also supports v4 signatures now. So the RS integration now works entirely in dev and should also be compatible with Garage.
Update: MVP of the dashboard is fully working now, allowing to revoke authorizations and launch apps with storage-first flow.
1960f39073to9a9947f9adMore updates:
start_urlfrom Web App Manifest when launching apps from the Storage dashboardChanges look all good. Great job 🙌
So far I wasn't able to test it though.
When running
docker compose up, I get the following error from theaccounts-ldap-1instance:I deleted all my old containers and images, but that didn't help.
@@ -0,0 +4,4 @@</div><div class="flex-grow"><h4 class="mb-1 text-lg font-bold"><%= @web_app.name %>Maybe it might be nice to also link the name or the client_id field directly to the launch URL? Just to easier open the app without having to go via the dropdown.
If you want to start with a fresh LDAP container (or Rails, after switching from running it on the host), you also have to delete the files in
./tmpfirst.However, if the documented quick start commands are not working on a fresh repo checkout, please file an issue for that, and I'll check it out asap!
@galfert Were you able to run it in the meantime?