-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't apply all migrations when starting in docker #45
Comments
Same. Bummer though. This would have fulfilled 120% of my use case. |
Same here. |
Having the same issue |
+1, I ran into the same issue. I switched to https://github.com/pypiserver/pypiserver. Doesn't have a nice gui and user nice management, but it does the job effectively enough. |
Still happening. |
Just verified when researching #54 , this is still the case for the postgres configuration. |
Unfortunately this issue made the whole package unusable, so I just used https://github.com/pypiserver/pypiserver. |
There is a simple way to circumvent this problem. It's not a propre fix, but it makes this package usable: launch the program a first time, and let it crash. Afterwards, manually add an entry into the "migrations" table to prevent the faulty migration from being applied: INSERT INTO migrations (id, name, ts) VALUES (8, 'packagefile_basename_unique.add_uniquie_basename_index', CURRENT_TIMESTAMP); Edit: Thanks to @ruohola for his suggestion about the usage of |
You could just use |
Could you please provide more detail to modify "migrations" table ? Thanks. |
I used the example
docker-compose.yml
file, and I get the following error during startup of the pypi container:The text was updated successfully, but these errors were encountered: