github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

On OS X chown 1000 $PWD/files breaks the Docker install #669

New Issue
Open
opened 2025-11-01 21:01:30 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-01 21:01:30 -05:00
Owner
Copy Link

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 /files gives a permissions error, as this owner (probably) does not exist.
Docker installation works properly on OS X without chown'ing /files or /db.
I found I also needed to add the port number to VIKUNJA_SERVICE_PUBLICURL in 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

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 `/files` gives a permissions error, as this owner (probably) does not exist. Docker installation works properly on OS X **without** `chown`'ing `/files` or `/db`. I found I also needed to add the port number to `VIKUNJA_SERVICE_PUBLICURL` in 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_
GiteaMirror commented 2025-11-01 21:01:31 -05:00
Author
Owner
Copy Link

@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!

@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!
GiteaMirror commented 2025-11-01 21:01:31 -05:00
Author
Owner
Copy Link

@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 left a comment (go-vikunja/vikunja#1679)
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!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@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 left a comment (go-vikunja/vikunja#1679) > 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! > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you authored the thread.Message ID: ***@***.***>
GiteaMirror commented 2025-11-01 21:01:31 -05:00
Author
Owner
Copy Link

@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 chown command.[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]

  • Note for macOS users: The default user ID on macOS is 501, not 1000, so you can skip the chown step or adjust it accordingly[3]
  • Also mention the VIKUNJA_SERVICE_PUBLICURL port number requirement you discovered[3]

Step 5: Propose Your Changes

Scroll to the bottom where you'll see a "Propose changes" form :[2][4]

  • Add a short, descriptive commit message (e.g., "Add macOS-specific Docker installation notes")
  • Provide a detailed description explaining what you changed and why[6][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]

  • The title should clearly describe your contribution
  • Add additional context in the description, referencing issue #1679[4][6]
  • Leave "Allow edits from maintainers" checked so the project maintainers can make minor adjustments if needed[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

@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 `chown` command.[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] - Note for **macOS users**: The default user ID on macOS is 501, not 1000, so you can skip the `chown` step or adjust it accordingly[3] - Also mention the `VIKUNJA_SERVICE_PUBLICURL` port number requirement you discovered[3] **Step 5: Propose Your Changes** Scroll to the bottom where you'll see a "**Propose changes**" form :[2][4] - Add a short, descriptive commit message (e.g., "Add macOS-specific Docker installation notes") - Provide a detailed description explaining what you changed and why[6][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] - The title should clearly describe your contribution - Add additional context in the description, referencing issue #1679[4][6] - Leave "**Allow edits from maintainers**" checked so the project maintainers can make minor adjustments if needed[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](https://docs.[github](https://github.com/go-vikunja/vikunja/issues/1679).com/en/repositories/working-with-files/managing-files/editing-files) [2](https://www.geeksforgeeks.org/git/how-to-create-pull-request-on-github-without-using-any-ide/) [3](https://github.com/go-vikunja/vikunja/issues/1679) [4](https://spinnaker.io/docs/community/contributing/docs/github-changes/) [5](https://gun.io/news/2024/11/a-complete-guide-to-github-forks-from-setup-to-pull-requests/) [6](https://docs.github.com/articles/creating-a-pull-request-from-a-fork) [7](https://docs.github.com/articles/fork-a-repo) [8](https://docs.github.com/articles/creating-a-pull-request) [9](https://docs.github.com/articles/about-pull-requests) [10](https://docs.github.com/en/codespaces/the-[github](https://github.com/go-vikunja/vikunja/issues/1679)dev-web-based-editor) [11](https://www.youtube.com/watch?v=nCKdihvneS0) [12](https://www.jetbrains.com/help/idea/work-with-[github](https://github.com/go-vikunja/vikunja/issues/1679)-pull-requests.html) [13](https://learn.microsoft.com/en-us/contribute/content/create-pull-request) [14](https://stackoverflow.com/questions/14821583/pull-request-without-forking) [15](https://stackoverflow.com/questions/73259187/received-a-pull-request-from-someone-else-how-to-edit-it-before-merging-directl) [16](https://www.youtube.com/watch?v=H2Hg8g0lWiE) [17](https://github.com/desktop/desktop/issues/17082) [18](https://www.reddit.com/r/github/comments/12kiour/how_can_i_change_multiple_files_in_one_pull/) [19](https://docs.github.com/de/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) [20](https://www.reddit.com/r/github/comments/104605y/if_i_made_a_pull_request_without_mergin_can_i/) [21](https://[github](https://docs.github.com/articles/creating-a-pull-request-from-a-fork).blog/changelog/2025-09-04-improved-file-navigation-and-editing-in-the-web-ui/)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#669
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?