Question about multi-location / multi-user sqlite setups
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, docker-compose, sqlite
- Domain
- databases, devops, infrastructure
Research direction
Start with tests/docker-compose.sqlite.yml and the added volume mapping to /var/www/wallabag/data/db, then inspect the container logs for the reported Exit code 1 and unhealthy status. Done would mean a documented, reproducible approach for sharing or moving the SQLite data and handling the two-location, multi-user setup.
Written by the indexing model from the issue text.
Description
Hello I'm a new Wallabag user and I just took example from this docker compose file to set up Wallabag with sqlite database.
Since in my use case I'll be in France or in Italy and will need to access my links also in case of faulty connection (or in case my raspberry goes down as sometimes might happen) I chose to avoid using maria-db. This would give me the option of easily migrating the saved images/files, with the sqlite database and just change the server url in the mobile app.
A first question about this setup: what composer entry could I use to store the sqlite database file with the rest of the data ? Alternatively how can I export/import the sqlite file from one container to the other to manually sync the two ?
Would it be necessary to wipe the android app cache at every server swap or just updating the sqlite and other files would be fine ?
Second issue: while in France I would be the only wallabag user while in Italy the users will be two.
To get a fast usable setup I simply created two separate containers for each user and two subdomains.
In this particular case are there other better solutions ?
Thanks for this wonderful tool. I've been looking for something like this for so long !
V.
EDIT: I just double checked for wallabag.sqlite file and added the following line to the volumes section of the docker compose file. - /DATA/AppData/wallabag/sqlite:/var/www/wallabag/data/db
Unfortunately, with that extra line, the container exits right after start and Portainer gives me Exit code 1 Status "Unhealty".
I'm not skilled enough (yet) to troubleshoot this. Any help will be greatly appreciated.
- Dominant language
- Shell
- Stars
- 771
- Forks
- 168
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wallabag/docker
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Awaiting response
Difficulty 4/5 3-5 days Newbie friendliness 32/100
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
Similar issues
-
Python Volcengine provider returns failures instead of raising themPossibly taken @Ricardo-M-L claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
agent-infra/sandbox#248 ·
-
chore priority:low size:S
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
celo-org/celopedia-skills#98 ·
Maintainers usually reply within 1 day
-
ready-for-pr
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kunchenguid/firstmate#7679 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MISP/misp-docker#478 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
t4t5/omdrop-owl#83 ·