Mixpost

[humptydumpty]

I updated from Mixpost Pro v.1.0.0 to v.1.2.0 using the official Mixpost update guide. But you need to do one thing beforehand, and another at the end to complete the steps on Cloudron.

Step 1: navigate to the mixpost folder before starting the update process

cd /app/data/mixpost-pro-team-app/

Step 2: follow update guide https://docs.inovector.com/books/mixpost-pro/page/in-your-standalone-or-laravel-app

Step 3: finish it off by running

 php artisan horizon

Done.

[humptydumpty]

Starting to hit storage issues. I received a backup failed notification. The app size was around 100MB for a fresh install. Now it's 3.98 GB! I'm not really using the app yet or uploading any media so the increase must be from the last update I did (v1.0 to v1.2).

Edit: The culprit is the log file located at /mixpost-pro-team-app/storage/logs/laravel.log (in my case it grew to over 5GB!). It had a lot of Redis references. The app's Redis is green in services and is using around 1/3 of the allocated 150MB so nothing out of the ordinary. The values in the .env file match what's in the credentials.txt file so that's good too. I'll update the post if Dima finds the root cause.

a few lines of the laravel.log file: https://pastebin.com/bkWK1LGA

[girish]

@humptydumpty maybe you can symlink that file to somewhere in /run so that it is not part of the backup.

[humptydumpty]

@girish I'll have to look into how I can accomplish that. Thanks for the hint!

Edit: I don't see a /run folder. Do you mean run.sh?

Edit 2: I think I found out how to do it via the run.sh method: https://docs.cloudron.io/apps/lamp/#custom-startup-script

The example on that page is:

# create symlinks
rm -rf /app/data/var/cache
mkdir -p /run/cache
ln -sf /run/cache /app/data/var/cache

correct me if I'm wrong, but for my use case it should be something like:

# create symlinks
rm -rf /app/data/mixpost-pro-team-app/storage/logs
mkdir -p /run/logs
ln -sf /run/logs /app/data/mixpost-pro-team-app/storage/logs

Edit 3: The app started fine with the code above in run.sh. Now, it looks like this in the file manager, so I guess it's working.

@girish I can't open the logs folder in the file manager; clicking on it does nothing. I'm worried that the log file will get too large and will require manual deletion in the future. What's the easiest way to access the folder or better yet, a way to auto-delete the log file after x days?

[humptydumpty]

@girish what's the file location for the /run folder that I symlinked earlier? I logged in via SFTP using FileZilla and can see the all the server folders (/) but haven't been able to locate the symlinked folder.

[girish]

@humptydumpty that sftp looks suspect. Only the /app/data directory is exposed via SFTP and not the entire container filesystem. Looks like you are logged in somewhere else.

There is no way to browse /run etc via SFTP. You have to use the Web Terminal.

[humptydumpty]

@girish I'm logging in as root and I'm positive that the IP is my Contabo VPS. On first login, the page looks like this.

Then, I can click on / and it shows this:

Any way, there's no way to access the /logs folder now via the web terminal in Cloudron dashboard. It's showing a grey file icon and double-clicking or right-clicking > open, does nothing. Brain fart! You're saying web terminal and I'm even typing it but thinking of the file manager Nevermind!

[humptydumpty]

To continue on the root SFTP access thing, I can see /box and /boxdata in the /yellowtent folder.

Should I be concerned about this?

[girish]

@humptydumpty said in Mixpost:

Should I be concerned about this?

concerned about? you are browsing the server's filesystem. The app runs as a container and has it's own filesytem. The app's filesystem is difficult to browse via SFTP.

[humptydumpty]

Ah, noted. I misunderstood what you meant and thought that I shouldn't have been able to browse/see the server folders. Thanks for bearing with me!

[jdaviescoates]

Any updates/ progress on getting this into the App Store? Could @Staff or any other @appdev help it along?

@lao9s I will buy a Pro licence as soon as this is in the Cloudron App Store

(also still kicking myself I didn't get a lifetime one while I could even though I still wouldn't've been able to use it yet )

[girish]

@jdaviescoates https://forum.cloudron.io/post/70435 still remains valid. It's not possible to package this for Cloudron .

[jdaviescoates]

@girish said in Mixpost:

It's not possible to package this for Cloudron

Any chance you can change the way it works @lao9s ?

[rmdes]

Still really exciting to see this up and running on cloudron with hands on approach using the LAMP, I'm definitely going to try this out

[robi]

@girish said in Mixpost:

@jdaviescoates https://forum.cloudron.io/post/70435 still remains valid. It's not possible to package this for Cloudron .

That's not quite entirely true, no? There is a writable part in /app/data and /var/run. It could be excluded from backups too depending on what directory it is downloaded to, say a hidden .pro dir.

It's also possible to create an in-memory file system, and have it download the Pro version there at every start. Otherwise it's the lite version.

[humptydumpty]

@robi I wish this can get sorted out. Keeping up with updates manually is a real PITA.

[robi]

I started a guide for Mixpost Lite in this thread:
https://forum.cloudron.io/topic/11088/mixpost-lite-install-guide-for-lamp-app

Let me know if I missed something.

[andreasdueren]

@robi said in Mixpost:

I started a guide for Mixpost Lite in this thread:
https://forum.cloudron.io/topic/11088/mixpost-lite-install-guide-for-lamp-app

Let me know if I missed something.

BTW this also works no problem in the enterprise version.

[humptydumpty]

[andreasdueren]

I honestly don't know how much sense it makes to package this. It seems to run super smooth in the LAMP app and there are so many different versions to keep up with packaging