-
Notifications
You must be signed in to change notification settings - Fork 12
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
Breaking changes in upcoming Polaris 0.13 #2
Comments
@agersant Thanks! When you publish the new version I'll do the changes to docker 😉 |
tried simply bump version in -POLARIS_VERSION := 0.12.4
+POLARIS_VERSION := 0.13.0 It compiles but can't load database on start, then I did following steps to make it work:
|
Apologies for the null songs, I forgot to document this as a breaking change. I'll update the release notes. |
New version published! Take note that now the database is, by default, in |
Hello!
I am opening this issue to give a heads up that I am thinking of making the Polaris
0.13
release soon-ish (depending on how quickly I can button up the migration from Rocket to Actix). One thing that did change since0.12.4
is the installation process on Linux. The installation directories and how they are decided have changed, to be more flexible and more standard-compliant. I expect these changes will have some impact on the Docker setup too.These changes affect:
The previous logic to determine these locations was, in order of priority:
-w
for web client directory)The new logic is, in order of priority:
-w
for web client directory)The corresponding compile-time environment variables are:
POLARIS_DB_DIR
POLARIS_WEB_DIR
POLARIS_SWAGGER_DIR
POLARIS_CACHE_DIR
POLARIS_LOG_DIR
POLARIS_PID_DIR
For reference, the supported command lines arguments are:
-d
or--database
for database file-w
or--web
for web client directory-s
or--swagger
for swagger directory--cache
for cache directory (polaris
will createthumbnails
directory inside if necessary)--log
for log file--pid
for pid fileThe former
log
option is now--log-level
(also a breaking change).PR discussing these changes: agersant/polaris#91
The text was updated successfully, but these errors were encountered: