mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-03-09 07:13:35 -05:00
On OS X chown 1000 $PWD/files breaks the Docker install #669
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/vikunja#669
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @theapiarist on GitHub (Oct 17, 2025).
Description
The default user on Mac OSX has the ID 501 (confirmed on several machines using
id -u).Setting the owner ID on OS X to 1000 of
/filesgives a permissions error, as this owner (probably) does not exist.Docker installation works properly on OS X without
chown'ing/filesor/db.I found I also needed to add the port number to
VIKUNJA_SERVICE_PUBLICURLin the docker-compose.yml to avoid an 'unauthorized' error when creating the user account.Thanks for the software, just what I was looking for 😄.
Vikunja Version
Version: v1.0.0-rc2
Browser and version
No response
Can you reproduce the bug on the Vikunja demo site?
No
Screenshots
No response
@kolaente commented on GitHub (Oct 19, 2025):
This sounds less like a bug, more like an update to the docs?
The docs repo is here: https://github.com/go-vikunja/website/
Would love a PR!
@theapiarist commented on GitHub (Oct 20, 2025):
Yes, a docs update, not a bug, apologies.
If I knew how to create a PR, I would, but I don’t 😞.
On 19 Oct 2025 at 10:15 +0100, kolaente @.***>, wrote:
@kolaente commented on GitHub (Oct 20, 2025):
Basically, you'd need to find the page where the information is missing here in this repo: https://github.com/go-vikunja/website/tree/main/src/content/docs/setup
Then, use the edit button on the top right to make changes. GitHub will prompt you to fork it and propose a PR with your changes.
Here's a personalized how-to made by perplexity:
https://www.perplexity.ai/search/explain-to-the-user-how-to-mak-vjNFJPwXTqeV.g8YZYrgAg#0
Here's a comprehensive explanation you can provide to help the user create a PR using GitHub's web interface:
Creating a Pull Request via GitHub Web Interface
Step 1: Navigate to the Documentation File
First, you'll need to find the specific file in the documentation that needs updating. Browse through the Vikunja documentation source files here: https://github.com/go-vikunja/website/tree/main/src/content/docs/setup[1][2]
Look for the Docker installation guide or macOS-specific setup instructions that need the correction about the
chowncommand.[3]Step 2: Click the Edit Button
Once you've found the file that needs updating, click the pencil icon (Edit this file) in the top-right corner of the file view.[2][4][1]
Step 3: GitHub Will Prompt You to Fork
Since you don't have write access to the original repository, GitHub will automatically detect this and show a message explaining that it will create a fork in your account. Click the button to proceed with forking.[5][6][7]
Step 4: Make Your Changes
Use GitHub's web-based Markdown editor to add the macOS-specific information. You might want to add something like:[4][1]
chownstep or adjust it accordingly[3]VIKUNJA_SERVICE_PUBLICURLport number requirement you discovered[3]Step 5: Propose Your Changes
Scroll to the bottom where you'll see a "Propose changes" form :[2][4]
Click the green "Propose changes" button.[4][2]
Step 6: Create the Pull Request
GitHub will take you to a "Comparing changes" page where you can review your edits. Click "Create pull request".[6][2][4]
On the next page, you'll see a form to finalize your PR :[8][6]
Click "Create pull request" one final time, and you're done ![2][6]
The maintainers will be notified and can review your proposed documentation improvements.[9][8]
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21