dependabot[bot] on npm_and_yarn
Bump ws from 6.2.1 to 6.2.2 Bu… (compare)
messages.en.ymlfor my suggested changes, or do I have to do anything more? I noticed that the translations have a "Translated using Weblate" as a recent comment which makes me think that they are being generated automatically. I want to make sure my submissions don't break anything, nor do they get overwritten
git checkout 2.4.2first. Unless there's some way to stop "make install" from always using the latest release, it seems the only way to install a specific v2 release is to install from the precompiled tarballs?
export ENV=prod SYMFONY_ENV=$ENV $COMPOSER_COMMAND install --no-dev -o --prefer-dist php bin/console wallabag:install --env=$ENV
Hi everyone! I'm brand new to wallabag and unfortunately I'm having some trouble with the initial spinup of the docker installation. I've searched through the chat history here, along with the github repo, and can't pinpoint the source of this error.
I'm adding wallabag to an existing
docker-compose, running on a Synology (Linux) with docker version 10.09.8. DB is a mariadb, reverse proxy is Traefik. I've tried folder permission modifications, removed the forward auth on the reverse proxy. I'm sure it's something stupid on my end.
^ This is from two startup attempts. The second time, I waited, then tried to go to the URL, and got an error 500 (can be seen in logs too). My MariaDB has no data inside the newly created table for wallabag. The mounted volume has no files in it either
wallabag: image: wallabag/wallabag container_name: ourgreatfamilyweb-Wallabag environment: # - MYSQL_ROOT_PASSWORD=wallaroot - SYMFONY__ENV__DATABASE_DRIVER=pdo_mysql - SYMFONY__ENV__DATABASE_HOST=192.168.14.251 - SYMFONY__ENV__DATABASE_PORT=3306 - SYMFONY__ENV__DATABASE_NAME=wallabag - SYMFONY__ENV__DATABASE_USER=wallabag - SYMFONY__ENV__DATABASE_PASSWORD=$WALLABAG_DB_PASS - SYMFONY__ENV__DATABASE_CHARSET=utf8mb4 - SYMFONY__ENV__MAILER_HOST=$SMTP_host - SYMFONY__ENV__MAILER_USER=$SMTP_email - SYMFONY__ENV__MAILER_PASSWORD=$SMTP_PW - SYMFONY__ENV__FROM_EMAIL=$SMTP_email - SYMFONY__ENV__DOMAIN_NAME=https://wallabag.ourgreatfamilyweb.com - SYMFONY__ENV__SERVER_NAME="ourgreatfamilyweb" ports: - 8090:80 volumes: - $CLOUDDIR/wallabag/images:/var/www/wallabag/web/assets/images restart: unless-stopped networks: - traefik_external labels: - "traefik.enable=true" ## HTTP Routers - "traefik.http.routers.wallabag-rtr.entrypoints=https" - "traefik.http.routers.wallabag-rtr.tls=true" - "traefik.http.routers.wallabag-rtr.rule=Host(`wallabag.$DOMAINNAME`)" ## Middlewares - "traefik.http.routers.wallabag-rtr.middlewares=chain-no-auth@file" ## HTTP Services - "traefik.http.routers.wallabag-rtr.service=wallabag-svc" - "traefik.http.services.wallabag-svc.loadbalancer.server.port=80"
(domain changed for privacy)
Hi guys, another question, different issue. This is more of a would-be-nice-to-know, and not a show-stopper. Anyway, for the curious...
I attempted to upgrade a Wallabag v2.3.8 instance (installed using precompiled tarball) to a v2.4.2 install from source (both with the same PostgreSQL backend).
It did not work. To be honest, I did not really expect it to, it was more of a "let's try and see what happens" :-)
What happened was multiple errors during the
doctrine:migrations:migrate step of the
make update process:
Cardinality violation: 7 ERROR: more than one row returned by a subquery.
My question is simply: is this what you would expect too? Or is there a way to switch an existing Wallabag installed using precompiled tarball to an install from source?
(And why would I want to do this? Primarily, I think it'd be easier to Ansiblify/script the upgrade steps of an install from source).