Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
J
@girish Thank you! I will give that a shot.
This sounds like it should be a part of the build package and/or the registry package, depending on use case.
I have added cloudron update --appstore-id {id} for the next release.
@girish Thanks so much for the great answers.
I look forward to installing the cloudron cli on my computer running Linux Mint 🤠.
S
Confirmed working on 4.5.3
To install a specific version: sudo npm install -g cloudron@4.5.3
M
node --version said v8.10.0, updated to v12.18.3 for good measure 😉
Ok this is fixed, however requires a new Cloudron release, since the tasks API needs a proper pending state.
Glad it solved itself 🙂
I have fixed the opn issue but rewriting to reuse the request issue is a much larger task. Bit unfortunate they deprecated such a popular module.
What if I want to keep each build service associated to each Cloudron instance respectively?
I would also delete ~/.cloudron.json for good measure since we change the format of the config a few times and maybe you have something from an older CLI version.
