Missing mariadb compose file #27

New Issue

2022-05-19T21:33:10Z

aadil commented

2022-05-19 21:33:10 +00:00

❯ abra app deploy files.aadils.computer
FATA[0007] open /home/aadil/.abra/recipes/nextcloud/compose.mariadb.yml: no such file or directory

did I miss a step or something? Here's how I tried to set it up:

abra app new nextcloud -S
abra app config files.aadils.computer (update url in config file)
abra app deploy files.aadils.computer

```sh ❯ abra app deploy files.aadils.computer FATA[0007] open /home/aadil/.abra/recipes/nextcloud/compose.mariadb.yml: no such file or directory ``` did I miss a step or something? Here's how I tried to set it up: 1. `abra app new nextcloud -S` 2. `abra app config files.aadils.computer` (update url in config file) 3. `abra app deploy files.aadils.computer`

decentral1se commented

2022-05-20 06:53:12 +00:00

Soooo, some work just went down on the database stuff in #26 /cc @yksflip and I believe you need to do this in your .env file:

COMPOSE_FILE="compose.yml"
COMPOSE_FILE="$COMPOSE_FILE:compose.mariadb.yml"

This should have been covered in the .env.sample file you received on new app creation but maybe you created it before this upgrade work happened? Unsure.

nextcloud/.env.sample Lines 8 to 10 in 801e0a0762

COMPOSE_FILE="compose.yml"

COMPOSE_FILE="$COMPOSE_FILE:compose.mariadb.yml"

#COMPOSE_FILE="$COMPOSE_FILE:compose.postgres.yml"

Other work-arounds may be doing something like:

cd ~/.abra/recipes/nextcloud
git checkout main
git pull origin main

Unsure of your local git repository state, it could be confusing abra potentially.

Soooo, some work just went down on the database stuff in https://git.coopcloud.tech/coop-cloud/nextcloud/pulls/26 /cc @yksflip and I believe you need to do this in your `.env` file: ``` COMPOSE_FILE="compose.yml" COMPOSE_FILE="$COMPOSE_FILE:compose.mariadb.yml" ``` This should have been covered in the `.env.sample` file you received on new app creation but maybe you created it before this upgrade work happened? Unsure. > https://git.coopcloud.tech/coop-cloud/nextcloud/src/commit/801e0a0762df57b327e8fb8ccab5a7dc23c07fdc/.env.sample#L8-L10 Other work-arounds may be doing something like: ``` cd ~/.abra/recipes/nextcloud git checkout main git pull origin main ``` Unsure of your local git repository state, it could be confusing `abra` potentially.

aadil commented

2022-05-20 15:00:25 +00:00

hmm so I tried the git checkout main and git pull origin main, but when I run abra app deploy I get the same error. I checked the nextcloud recipe directory and it reverted to the previous git state.

hmm so I tried the `git checkout main` and `git pull origin main`, but when I run `abra app deploy` I get the same error. I checked the nextcloud recipe directory and it reverted to the previous git state.

decentral1se commented

2022-05-21 07:10:38 +00:00

Ah hmm, perhaps checking out the latest once more and running deploy -C?

I think we need to publish this new version in the catalogue which I will try to do soon.

Ah hmm, perhaps checking out the latest once more and running `deploy -C`? I think we need to publish this new version in the catalogue which I will try to do soon.

yksflip commented

2022-05-23 12:22:35 +00:00

hmm I thought I did that here maybe i did smth wrong?

hmm I thought I did that [here](https://git.coopcloud.tech/coop-cloud/recipes-catalogue-json/commit/b49e41600e73e7159c40ba545363c3ec16089817) maybe i did smth wrong?

decentral1se commented

2022-05-24 07:30:00 +00:00

hmm I thought I did that here maybe i did smth wrong?

Ah, nice! I deployed this by running make in ~/.abra/catalogue. I think only Autonomic people can actually deploy the changes at the moment 😿 We need to work out access or better, automation to get those changes out as they come in.

> hmm I thought I did that here maybe i did smth wrong? Ah, nice! I deployed this by running `make` in `~/.abra/catalogue`. I think only Autonomic people can actually deploy the changes at the moment 😿 We need to work out access or better, automation to get those changes out as they come in.

decentral1se commented

2022-05-24 07:31:13 +00:00

Also, please note folks, we've not really had several folks using a recipe ("operators") and several folks maintaining that recipe ("maintainers") at the same time before imho, so we're working this out as we go along 😆 Thanks for patience on these growing pains...

decentral1se commented

2022-05-24 10:44:54 +00:00

Oh, I mistakenly didn't deploy the changes 🦀 but @knoflook is picking this up 🤞

decentral1se commented

2022-05-24 12:23:57 +00:00

This should be fixed now! Ping on matrix chat if you want new catalogue changes deployed for now. Feel free to re-open if stuff is still borked!

decentral1se closed this issue

2022-05-24 12:23:57 +00:00

Sign in to join this conversation.

Branches Tags

main

update_33.0.8

renovate/pgautoupgrade-pgautoupgrade-18.x

renovate/docker.elastic.co-elasticsearch-elasticsearch-9.x

pr-15.2.0+34.0.2-fpm

pr-14.1.0+33.0.7-fpm

pr-14.2.0+33-fpm

pr-15.1.0+34.0.2-fpm

pr-15.0.0+34.0.2-fpm

pr-14.0.1+33.0.7-fpm

feat/check-major-upgrade

pr-14.0.0+33-fpm

temp

fix/nginx-conf-config-name

pr-13.2.0+32-fpm

renovate/redis-8.x

upload-limit

feature/imaginary

kc_stable

nextcloud-v28

add-theming-v28.0.5

add-theming

update-nginx-conf

split-bbb-onlyoffice-compos

split-onlyoffice-bbb-config

authentik_sso

healthchecks

occ_cmds

auto_app_install

embed_nextcloud_in_iframe

auto_configure_sso

add-postgres-db

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/nextcloud#27

	COMPOSE_FILE="compose.yml"
	COMPOSE_FILE="$COMPOSE_FILE:compose.mariadb.yml"
	#COMPOSE_FILE="$COMPOSE_FILE:compose.postgres.yml"