SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-05-16 05:02:26 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Change Database used for Wiki.JS #570

New Issue
Closed
opened 2025-11-20 04:50:22 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 04:50:22 -05:00
Owner
Copy Link

Originally created by @dave-yap on GitHub (Feb 20, 2025).

📌 Task summary

DBs other than PostgreSQL are said to not be supported in next versions

📋 Task details

Currently the script utilizes SQLite for its database. I had a look around the documentations of Wiki.JS and it seems to not be recommended for production environments either. There is a huge disclaimer stating that only PostgreSQL will be supported in the next major version of the application too. Maybe it can be used, but won't be ideal? Not sure if there will be issues with upgrading in the future.

Source: https://docs.requarks.io/install/requirements

Originally created by @dave-yap on GitHub (Feb 20, 2025). ### 📌 Task summary DBs other than PostgreSQL are said to not be supported in next versions ### 📋 Task details Currently the script utilizes SQLite for its database. I had a look around the documentations of Wiki.JS and it seems to not be recommended for production environments either. There is a huge disclaimer stating that only PostgreSQL will be supported in the next major version of the application too. Maybe it can be used, but won't be ideal? Not sure if there will be issues with upgrading in the future. Source: https://docs.requarks.io/install/requirements
saavagebueno added the external label 2025-11-20 04:50:22 -05:00
saavagebueno commented 2025-11-20 04:50:23 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 20, 2025):

We can't do nothing about it now, until they release a migration guide/tool

An export + import tool will be made available at / shortly after release.

We can probably change the script to stop updates until we update it to support new major release of WikiJS

@tremor021 commented on GitHub (Feb 20, 2025): We can't do nothing about it now, until they release a migration guide/tool `An export + import tool will be made available at / shortly after release.` We can probably change the script to stop updates until we update it to support new major release of WikiJS
saavagebueno commented 2025-11-20 04:50:23 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 20, 2025):

That's so sad that the export tool will only be introduced after the release, how did they envision that?

We should at least install psql so that x users already have it as a basis...

@MickLesk commented on GitHub (Feb 20, 2025): That's so sad that the export tool will only be introduced after the release, how did they envision that? We should at least install psql so that x users already have it as a basis...
saavagebueno commented 2025-11-20 04:50:23 -05:00
Author
Owner
Copy Link

@dave-yap commented on GitHub (Feb 20, 2025):

I'm wondering if there should be an update to the install script to include psql instead of sqlite by default for new installations.

I believe it'll help facilitate migrations/updates in the future. If there's an agreement, me or others can try having a look at refreshing the install script.

EDIT: Didn't see the PR at first, thanks for refreshing the script @MickLesk !

@dave-yap commented on GitHub (Feb 20, 2025): I'm wondering if there should be an update to the install script to include psql instead of sqlite by default for new installations. I believe it'll help facilitate migrations/updates in the future. If there's an agreement, me or others can try having a look at refreshing the install script. EDIT: Didn't see the PR at first, thanks for refreshing the script @MickLesk !
saavagebueno commented 2025-11-20 04:50:24 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 20, 2025):

Yea, @MickLesk pushed the preparation update, but we still have to wait for the official release to see how we will proceed

@tremor021 commented on GitHub (Feb 20, 2025): Yea, @MickLesk pushed the preparation update, but we still have to wait for the official release to see how we will proceed
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label external
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#570
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?