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

offline message prevents vikunja from running on local machine when there is no connectivity #125

New Issue
Closed
opened 2025-11-01 20:47:54 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-01 20:47:54 -05:00
Owner
Copy Link

Originally created by @jcvanhalle-ec on GitHub (Feb 10, 2023).

Description

I am running vikunja on my local machine, through docker, and it's configured to be available at http://127.0.0.1:10000/ (front-end) and http://127.0.0.1:10001/api/v1. So far, so good.

But vikunja detects the lack of network and/or internet connectivity and displays an offline message filling the whole screen and removes any way to interact with the page.

I don't think vikunja has a hard requirement for being always online so I think this offline message should not prevent from using vikunja on a local machine without connectivity.

Vikunja Frontend Version

0.20.2

Vikunja API Version

0.20.2

Browser and version

Firefox 102.5.0esr

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

image

Originally created by @jcvanhalle-ec on GitHub (Feb 10, 2023). ### Description I am running vikunja on my local machine, through docker, and it's configured to be available at http://127.0.0.1:10000/ (front-end) and http://127.0.0.1:10001/api/v1. So far, so good. But vikunja detects the lack of network and/or internet connectivity and displays an offline message filling the whole screen and removes any way to interact with the page. I don't think vikunja has a hard requirement for being always online so I think this offline message should not prevent from using vikunja on a local machine without connectivity. ### Vikunja Frontend Version 0.20.2 ### Vikunja API Version 0.20.2 ### Browser and version Firefox 102.5.0esr ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots ![image](https://user-images.githubusercontent.com/91598610/218058324-6feb4fdc-72f1-431b-9758-5c04389e0983.png)
GiteaMirror commented 2025-11-01 20:47:55 -05:00
Author
Owner
Copy Link

@dpschen commented on GitHub (Feb 10, 2023):

There is an env variable that you can set to disable this message for development.

@dpschen commented on GitHub (Feb 10, 2023): [There is an env variable that you can set](https://kolaente.dev/vikunja/frontend/src/branch/main/.env.local.example#L8) to disable this message for development.
GiteaMirror commented 2025-11-01 20:47:55 -05:00
Author
Owner
Copy Link

@dpschen commented on GitHub (Feb 10, 2023):

Some more info:
The reason why we currently show this message is to prevent data loss and prevent errors.

We do cache stuff locally but not in a way that is reliable. Also you won't be able to edit stuff (since you can't save). We want to get there but for now the only way is simple disable the overlay via setting that env. But expect errors!

@dpschen commented on GitHub (Feb 10, 2023): Some more info: The reason why we currently show this message is to prevent data loss and prevent errors. We _do_ cache stuff locally but not in a way that is reliable. Also you won't be able to edit stuff (since you can't save). We want to get there but for now the only way is simple disable the overlay via setting that env. But expect errors!
GiteaMirror commented 2025-11-01 20:47:56 -05:00
Author
Owner
Copy Link

@jcvanhalle-ec commented on GitHub (Feb 10, 2023):

Okay, thanks for the workaround and the explanation !

@jcvanhalle-ec commented on GitHub (Feb 10, 2023): Okay, thanks for the workaround and the explanation !
GiteaMirror commented 2025-11-01 20:47:56 -05:00
Author
Owner
Copy Link

@dpschen commented on GitHub (Feb 10, 2023):

Does that solve your issue? If so can you close it?

@dpschen commented on GitHub (Feb 10, 2023): Does that solve your issue? If so can you close it?
GiteaMirror commented 2025-11-01 20:47:58 -05:00
Author
Owner
Copy Link

@jcvanhalle-ec commented on GitHub (Feb 10, 2023):

It doesn't solve the issue but it's not a wontfix either and there is a workaround so I didn't really know which kind of closing to choose. I'll mark it as close as completed.

I can live with that behavior 99.99% of the time anyway I think.

@jcvanhalle-ec commented on GitHub (Feb 10, 2023): It doesn't solve the issue but it's not a _wontfix_ either and there is a workaround so I didn't really know which kind of closing to choose. I'll mark it as _close as completed_. I can live with that behavior 99.99% of the time anyway I think.
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#125
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?