Hi all,
I am wondering if we are far away from an addition of mailpiler to the Cloudron app repository. It would be of great help in a couple of the situation I am facing atm.
@vladimir-d Maybe you have had the chance to commit the working app version to Clourdon's GitLab already

If I can help (within the remit of my abilities) or contribute in making this happen, I would be happy to do so.

@echokos said in Umami - Failed container start with environment variables:

May 24 20:32:41 /app/data/env: line

I had something similar with IGNORE_IP when I lazily copied the variable from the umami doc (https://umami.is/docs/environment-variables)

try this FORCE_SSL=1 (without spaces)

and restart your app - This seems to work.

Hi - Thanks @ChristopherMag for the suggestion.
It seems as all importers have been gathered under the Firefly Data Importer app aka FIDI It think it would make sense to rename the topic accordingly as I was unable to find it upon an initial search in the whislist.

With the continuous Firefly development, I am of the view that this would also be very much of benefit to the Firefly on Cloudron package.

@darkben Hi Ben,

I beleive this to be related to https://forum.cloudron.io/topic/7489/umami-update-1-37-0-package-version-1-6-0-won-t-start-errors-in-logs

My understanding is that the upstream Umami developer(s) made some breaking changes in their previous release, leading to an automatic update not being possible. Please see the forum post for more details.

@girish published this breaking changes under app package 2.0 in Cloudron so that no automatic update would take place and thus avoid inoperable application without notice.
But the underlying situation remains.
See here: https://forum.cloudron.io/post/52142

Couple of "solutions" / workaround:

• uninstall current app and re-install fresh from cloudron app store -> this will lead to previous Umami data / configs / stats being lost and require a new configuration from all sites.
• install a second umami app package on cloudron, using a different subdomain/app name and run with the two package side by side -> this still requires a new configuration / migration of your sites to the new umami endpoint. However you can keep the stats in the old package (provided that you can revert the changes due to the update attempt).

Neither are ideal, but it least it gets you running again.

Hopefully this helps further.

Oh how I would love to have this packaged... Anyone started taking a look a putting this on Cloudron?
Happy to help any way I can within my abilities.

@LoudLemur
Not too sure about the naming here but here is my take:

• Documize Zerabase seems to be the commercial (closed source ?) option.
• Documize Community seems to be the self hosted/open source option.

Documize Zerabase aims indeed to be "is the all-in-one product delivery and insight discovery platform that provides product teams with a place to think, share and execute."

Documize Community aims instead to be "the enterprise-ready wiki and knowledge-base software. Simple, elegant, usable by both technical and non-technical people alike."

Personally, I am far more attracted by Documize Community at this stage than the Zerabase option which aims to encompass more than what would be useful for my use cases.

Hence, when I look at this, I do not think that comparing Documize Community to Zerabase/Odoo is entirely relevant, since not the same product.
But I am well aware that this is a personal view, that I might be wrong or that others Cloudronites (??) (Cloudronians ??) here might have a different take on this.

All I know: Documize Community (on paper at least) scratch the exact itch that I have in multiple use cases / scenarii, that other knowledge base / wiki products do not, or not entirely.

I have, as a plan, to try to give this a go outside of Cloudron for now, to see if indeed this delivers on what it advertises, but at last, I have not reach that stage in my to-do list.
Maybe others have and can comment?

All I know for sure, is that the convenience of having this packaged on Cloudron would be undeniable - for all that Cloudron brings and more...

Thanks for the suggestion

Please correct me if I am wrong but I do not think PicApport is open source, or is it?
Not that I am opposed to the idea, on the contrary as I think Cloudron could do with a better photo/video management app (other than Lychee).

Yet accessible source is still, in my opinion, a massive point for the integration of an app on Cloudron over another. Which is why, at this stage, my preference would go for something like Piwigo as an alternative (to Lychee / Photoprism - if still not integrable).

Of course, the above is moot if PicApport is indeed open source and I simply did not find it.

Also, the mention "Free for private users" on their website (they also mention to contact them for using the app as a company) makes me think that PicApport might not be suitable to the extend of use-cases that Cloudron is being used with. Other Cloudron users here might also have better insight.

Hi @girish - There have been a major update and two minor ones in the last 4 months. Might be worth revisiting ?
Unfortunately I lack the expertise to check this, but providing I have some time, I am always keen in helping.

I would value this as a great addition to Cloudron.

@darkben Hi Ben,

I beleive this to be related to https://forum.cloudron.io/topic/7489/umami-update-1-37-0-package-version-1-6-0-won-t-start-errors-in-logs

My understanding is that the upstream Umami developer(s) made some breaking changes in their previous release, leading to an automatic update not being possible. Please see the forum post for more details.

@girish published this breaking changes under app package 2.0 in Cloudron so that no automatic update would take place and thus avoid inoperable application without notice.
But the underlying situation remains.
See here: https://forum.cloudron.io/post/52142

Couple of "solutions" / workaround:

• uninstall current app and re-install fresh from cloudron app store -> this will lead to previous Umami data / configs / stats being lost and require a new configuration from all sites.
• install a second umami app package on cloudron, using a different subdomain/app name and run with the two package side by side -> this still requires a new configuration / migration of your sites to the new umami endpoint. However you can keep the stats in the old package (provided that you can revert the changes due to the update attempt).

Neither are ideal, but it least it gets you running again.

Hopefully this helps further.

@LoudLemur
Not too sure about the naming here but here is my take:

• Documize Zerabase seems to be the commercial (closed source ?) option.
• Documize Community seems to be the self hosted/open source option.

Documize Zerabase aims indeed to be "is the all-in-one product delivery and insight discovery platform that provides product teams with a place to think, share and execute."

Documize Community aims instead to be "the enterprise-ready wiki and knowledge-base software. Simple, elegant, usable by both technical and non-technical people alike."

Personally, I am far more attracted by Documize Community at this stage than the Zerabase option which aims to encompass more than what would be useful for my use cases.

Hence, when I look at this, I do not think that comparing Documize Community to Zerabase/Odoo is entirely relevant, since not the same product.
But I am well aware that this is a personal view, that I might be wrong or that others Cloudronites (??) (Cloudronians ??) here might have a different take on this.

All I know: Documize Community (on paper at least) scratch the exact itch that I have in multiple use cases / scenarii, that other knowledge base / wiki products do not, or not entirely.

I have, as a plan, to try to give this a go outside of Cloudron for now, to see if indeed this delivers on what it advertises, but at last, I have not reach that stage in my to-do list.
Maybe others have and can comment?

All I know for sure, is that the convenience of having this packaged on Cloudron would be undeniable - for all that Cloudron brings and more...

Oh how I would love to have this packaged... Anyone started taking a look a putting this on Cloudron?
Happy to help any way I can within my abilities.

@echokos said in Umami - Failed container start with environment variables:

May 24 20:32:41 /app/data/env: line

I had something similar with IGNORE_IP when I lazily copied the variable from the umami doc (https://umami.is/docs/environment-variables)

try this FORCE_SSL=1 (without spaces)

and restart your app - This seems to work.

Hi all,
I am wondering if we are far away from an addition of mailpiler to the Cloudron app repository. It would be of great help in a couple of the situation I am facing atm.
@vladimir-d Maybe you have had the chance to commit the working app version to Clourdon's GitLab already

If I can help (within the remit of my abilities) or contribute in making this happen, I would be happy to do so.

Thanks for the suggestion

Please correct me if I am wrong but I do not think PicApport is open source, or is it?
Not that I am opposed to the idea, on the contrary as I think Cloudron could do with a better photo/video management app (other than Lychee).

Yet accessible source is still, in my opinion, a massive point for the integration of an app on Cloudron over another. Which is why, at this stage, my preference would go for something like Piwigo as an alternative (to Lychee / Photoprism - if still not integrable).

Of course, the above is moot if PicApport is indeed open source and I simply did not find it.

Also, the mention "Free for private users" on their website (they also mention to contact them for using the app as a company) makes me think that PicApport might not be suitable to the extend of use-cases that Cloudron is being used with. Other Cloudron users here might also have better insight.

Hi @girish - There have been a major update and two minor ones in the last 4 months. Might be worth revisiting ?
Unfortunately I lack the expertise to check this, but providing I have some time, I am always keen in helping.

I would value this as a great addition to Cloudron.

Hi - Thanks @ChristopherMag for the suggestion.
It seems as all importers have been gathered under the Firefly Data Importer app aka FIDI It think it would make sense to rename the topic accordingly as I was unable to find it upon an initial search in the whislist.

With the continuous Firefly development, I am of the view that this would also be very much of benefit to the Firefly on Cloudron package.