-
Jul 22 10:37:23 Starting SickChill... Jul 22 10:37:23 Checking poetry Jul 22 10:37:23 Current environment is not writable! Jul 22 10:37:23 Source dir is not writable by this user either, we cannot continue: f/app/code/sickchill Jul 22 10:37:25 Starting SickChill... Jul 22 10:37:25 Checking poetry Jul 22 10:37:25 Current environment is not writable! Jul 22 10:37:25 Source dir is not writable by this user either, we cannot continue: f/app/code/sickchillSickchill is sometimes tricky ...
-
Jul 22 10:37:23 Starting SickChill... Jul 22 10:37:23 Checking poetry Jul 22 10:37:23 Current environment is not writable! Jul 22 10:37:23 Source dir is not writable by this user either, we cannot continue: f/app/code/sickchill Jul 22 10:37:25 Starting SickChill... Jul 22 10:37:25 Checking poetry Jul 22 10:37:25 Current environment is not writable! Jul 22 10:37:25 Source dir is not writable by this user either, we cannot continue: f/app/code/sickchillSickchill is sometimes tricky ...
-
I revoked the last release now, this seems a bit more involved to fix, since apparently the app now requires to use pip virtualenv to install packages, which will not work in the read-only filesystem, so we have to somehow fixup the virtualenv usage.
-
I revoked the last release now, this seems a bit more involved to fix, since apparently the app now requires to use pip virtualenv to install packages, which will not work in the read-only filesystem, so we have to somehow fixup the virtualenv usage.
-
@nebulon How can I roll back to the previous version ?
Also, any idea how a completely broken package slipped through your CI tests ?
@mehdi you would have to restore to the previous version or if you don't have any old backups, alternately "update" to an older version, in-place with
cloudron update --app <yourappdomain.com> --appstore-id io.github.sickchill.cloudronapp@1.3.0Have to investigate how the release was able to get published indeed.
-
@mehdi you would have to restore to the previous version or if you don't have any old backups, alternately "update" to an older version, in-place with
cloudron update --app <yourappdomain.com> --appstore-id io.github.sickchill.cloudronapp@1.3.0Have to investigate how the release was able to get published indeed.
-
I learnt a few things about the python world as part of fixing this:
-
There is now something called poetry. Projects now contain a poetry.toml file which can be converted into a requirements.txt using
poetry export --format requirements.txt > requirements.txt. -
There is something called an "editable install" - https://www.python.org/dev/peps/pep-0660/ . Idea being you can just run the code and the code just "installs" away packages as needed. See https://www.python.org/dev/peps/pep-0660/#id5 .
-
pyproject.toml is some new project settings file that possibly replaces setup.py
-
-
G girish has marked this topic as solved on
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login