Closed NightHawkATL closed 3 months ago
I added the quarkus.native.march=compatibility flag, do you mind testing with the binary from this CI build/the docker master-<database>
tag? If it works I'll release 5.0.1.
I added the quarkus.native.march=compatibility flag, do you mind testing with the binary from this CI build/the docker
master-<database>
tag? If it works I'll release 5.0.1.
I am not seeing a docker binary.
Sorry, maybe I wasn't clear. Only binaries are published on that page, Docker CI builds are published directly on Docker Hub with the master-<database>
tag.
sorry. will work on that.
I was able to get "master-postgresql" to load for me. It works with my processor now.
I also noticed that the new compose didn't mention a volume for the commafeed service and there is no longer mention of PGID & PUID but I added all of that to my stack for deployment.
services:
commafeed:
image: athou/commafeed:master-postgresql
restart: unless-stopped
container_name: commafeed
environment:
- QUARKUS_DATASOURCE_JDBC_URL=jdbc:postgresql://postgresql:5432/commafeed
- QUARKUS_DATASOURCE_USERNAME=commafeed
- QUARKUS_DATASOURCE_PASSWORD=*Redacted*
- PGID=1000
- PUID=1000
volumes:
- /portainer/Files/AppData/Config/commafeed/data:/commafeed/data
deploy:
resources:
limits:
memory: 256M
ports:
- 8082:8082
postgresql:
image: postgres:latest
container_name: commafeed_db
restart: unless-stopped
environment:
POSTGRES_USER: commafeed
POSTGRES_PASSWORD: *Redacted*
POSTGRES_DB: commafeed
PGID: 1000
PUID: 1000
volumes:
- /portainer/Files/AppData/Config/commafeed/db:/var/lib/postgresql/data
I was able to get "master-postgresql" to load for me. It works with my processor now.
Awesome, thanks! I'll release 5.0.1.
I also noticed that the new compose didn't mention a volume for the commafeed service
The volume is now only needed when the H2 file-based database is used. Since you're using postgresql, you don't need to mount the volume.
and there is no longer mention of PGID & PUID but I added all of that to my stack for deployment.
I believe those were never mentioned. There is an issue for that here: https://github.com/Athou/commafeed/issues/1227
thank you!
Describe the bug Lots of support issues with a processor that I have been using for some time.
To Reproduce Upgrade to the latest with the above CPU
Expected behavior That I would still be able to use it after the upgrade
Screenshots
Environment (please complete the following information):
Additional context Guess I'll have to stay on the older version until this is fixed or not.