Mixpost
-
Hi @girish
The Lite version is not upgradable to Pro with a key, the Pro is a different package.
Some specific technical data about Pro:
The Pro version is installing only with a License code on starting the container. In other words, the entire code of Mixpost Pro is not in the image but is downloaded from the private repository every time the container is started.The doc: https://docs.inovector.com/books/mixpost-pro-team/page/using-docker-image
Is such an approach possible on Cloudron?
-
The Pro version is installing only with a License code on starting the container. In other words, the entire code of Mixpost Pro is not in the image but is downloaded from the private repository every time the container is started.
Ah, I see. That approach won't work well on Cloudron. All our containers run on readonly file system
I guess one can download code and run but that will make updates and backups quite tricky. -
@girish I got it. Can you tell me how other paid software works in this case?
So in the case of Mixpost Pro, it is important that:
- Users only have access to the code with a license key.
- The application cannot be installed without a license code.
What solutions do you recommend?
Thank you!
-
Does anyone here have an implementation up and running who is willing to share their docs/additional steps?
Also, has anyone happened to get an implementation working using the Cloudron Proxy?
-
@girish I got it. Can you tell me how other paid software works in this case?
From the apps that we have:
- confluence - we can download the code (https://www.atlassian.com/software/confluence/download-archives) . When it starts up, you provide a license
- onlyoffice ee - code can be installed from apt (https://git.cloudron.io/cloudron/onlyoffice-ee-app/-/blob/master/Dockerfile). it picks up license from a file on startup
- mattermost - https://mattermost.com/download/
- gitlab/cloudron - apart from above which have binaries that are downloaded, both gitlab (https://gitlab.com/gitlab-org/gitlab) and cloudron (https://git.cloudron.io/cloudron/box) are source available. but needs license to do extra things. yes, this does mean that one can read the code and bypass license. We considered this and decided not to worry about such people and tackle it if it's a real problem (so far, it's not). GitLab EE has https://docs.gitlab.com/ee/administration/license_file.html
In all the cases, one can install the app but simply not use it without a license.
-
@girish I am messing around with deploying Mixpost in a LAMP app and have gotten the config to work the Apache and SQL but i am having trouble with Redis
In the Cloudron docs is shows how to connect to MySQL via the local docker port: 172.18.30.1What is the local IP for Redis? or best method to have a LAMP app connect to Redis?
It looks like a container instance of Redis is spun up per app?
-
On Cloudron the apps get all the addon service credentials and connection details as environment variables in the container. So just open a webterminal into the app instance and run
envMore info at https://docs.cloudron.io/packaging/addons/
-
@plusone-nick Are you using Mixpost Lite or Pro?
-
i am using pro
-
@nebulon I guess I am a bit confused as I am aware of the credentials.txt and see the Redis config but don't understand what "URL" or IP i should use.
Both SQL and Redis have their respective protocols in their URL: mysql:// and redis://
Am i supposed to use that URL for Redis vs the local Docker IP provided like for SQL? I kinda figured Redis would have an IP i could also use.
✌💙+1
-
@plusone-nick The redis IP is dynamic, so you should connect to it by name. You can use the credentials in
/app/data/credentials.txt(this is the same as the env vars). Does that not work? -
@girish Got horizon installed, but it soon kills as there is no schedule set. The Mixpost instructions advise setting a mixpost-horizon.conf in /etc/supervisor/conf.d but as you know its read only.
What is the best method to approach this?
-
EDIT: Apologies I got the Schedule going with the cron job... It's the Horizon/Supervisor config at /etc/supervisor/conf.d which is the last blocker
-
Go, Nick. Go!
-
@humptydumpty lol 🫡
Final update for now: got all services "UP" and "working"
BUT... - still need to have Horizon/Supervisor Config set as it only stays alive for a little, in that time I was able to push some posts through
Dwindled down from 38 to 7 errors – something regarding: Illuminate & Symfony
[2023-08-06 22:56:13] production.ERROR: Not enough arguments (missing: "name"). {"exception":"[object] (Symfony\Component\Console\Exception\RuntimeException(code: 0): Not enough arguments (missing: "name"). at /app/data/mixpost-pro-team-app/vendor/symfony/console/Input/Input.php:76)
[stacktrace]
#0 /app/data/mixpost-pro-team-app/vendor/symfony/console/Command/Command.php(321): Symfony\Component\Console\Input\Input->validate()
#1 /app/data/mixpost-pro-team-app/vendor/laravel/framework/src/Illuminate/Console/Command.php(181): Symfony\Component\Console\Command\Command->run()
#2 /app/data/mixpost-pro-team-app/vendor/symfony/console/Application.php(1081): Illuminate\Console\Command->run()
#3 /app/data/mixpost-pro-team-app/vendor/symfony/console/Application.php(320): Symfony\Component\Console\Application->doRunCommand()
#4 /app/data/mixpost-pro-team-app/vendor/symfony/console/Application.php(174): Symfony\Component\Console\Application->doRun()
#5 /app/data/mixpost-pro-team-app/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(201): Symfony\Component\Console\Application->run()
#6 /app/data/mixpost-pro-team-app/artisan(37): Illuminate\Foundation\Console\Kernel->handle()
#7 {main}
"}✌💙+1
-
@plusone-nick said in Mixpost:
[2023-08-06 22:56:13] production.ERROR: Not enough arguments (missing: "name"). {"exception":"[object] (Symfony\Component\Console\Exception\RuntimeException(code: 0): Not enough arguments (missing: "name"). at /app/data/mixpost-pro-team-app/vendor/symfony/console/Input/Input.php:76)
this seems like some CLI is expecting more arguments (specifically --name or something)
