Hey there @xeruf! I'll certainly add this to the docs, but since the common
library is being used, any values that can be found within applications at [kubesearch.dev](https://kubesearch.dev/#bjw…
Well feel free to reach out if you're still having any issues. Taking the latest version of the Helm chart and deploying it with no values: ![image](/attachments/205cf6d4-b284-40ef-b4d1-e47f240090…
Are you able to provide the values that you're providing to the Helm chart to create your release @xeruf?
Looking through my logs, I don't see anything to indicate that anything weird/bad happened when trying to create the table? In order of oldest logs to new, for anything related to migration
:
![i…
I restarted the pod a few more times to add the DEBUG
values to get more interesting output:
# Debugging values
- name: VIKUNJA_LOG_DATABASE
value:…
Oh, no it did not! In the screenshot here (vikunja/api#1655 (comment)), these are all the tables in the DB.
Or if you work for a company, and you get tasks within a project assigned to you. How do you about organizing your tasks? The only way would be through a Saves Filter to see your tasks, but how…
I removed the 20230913202615
from the migrations
table, and then restarted the API container. It then created the new entry as expected:
![image](/attachments/18855dba-f9ce-4326-859f-295820f56…
Well perhaps it would be easier to replicate if I lay out what I was trying to accomplish:
- Vikunja1 (v0.21.0) create export of your data via the GUI
- Vikunja2 (unstable, no data whatsoever)…
I should've just done a SELECT
statement then looking at it via my eyeballs, yep, that migration is there then.
I'm assuming that the relation "webhooks" does not exist
error is because of…
OR if I'm just off my rocker, how would you suggest going about combining multiple Projects in a single view, and being able to organize the results?
I feel like a broken record always coming to you with: "Hey brand new setups are broken w/ Postgres because of " 😅
I'm not sure if I'm just cursed or if it's just me lol
So it doesn't look like 20230913202615
was created/run then...
This was just a "fresh" Vikunja running the latest unstable api/frontend, with a completely empty DB. So I'm assuming that the…