Guidance needed: Best practices for migrating a virtual mashine winget.pro deployment (Nginx/Gunicorn/SQLite) #6358
slavamv
started this conversation in
Configuration
Replies: 1 comment
-
|
You may want to reach out to the actual
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello! I need to migrate an existing virtual machine
winget.prodeployment to the production sever. I have about 85GB of manually downloaded packages (heavy enterprise installers like .exe, .msi, and .zip) and want to ensure a smooth transition without breaking paths or corrupting the database.Current Environment Details:
unix:/var/run/django/gunicorn.sock)/srv/)django.db.backends.sqlite3)Migration Questions:
rsyncthe.sqlite3file to the new server, or do you recommend using Django'sdumpdata/loaddatafor a winget.pro specific migration?rsync -avzsufficient to move the entire/srv/directory to the new host, or are there specific symlinks, hardlinks, or ownership permissions (e.g., for thedjangouser) I must strictly recreate?unix:/var/run/django/gunicorn.sock. When setting up the new server, what is the standard method or script provided by winget.pro to generate the Gunicorn systemd service so that the socket is created with the correct permissions?Any advice, scripts, or documentation links for migrating a bare-metal setup would be highly appreciated. Thank you!
Beta Was this translation helpful? Give feedback.
All reactions