Mixpost
-
@humptydumpty you can't use the variables until you set them in the .env file
so you have to remove the placeholders like "CLOUDRON_MYSQL_DATABASE" and put the value for that variable which is located in /app/data/credentials.txt
They are like 16 and 32 characters long -
OK, I made the changes and this is my .env file:
Still, step 7 with same error.
-
I think I'm doing Step 7 wrong. Do you paste all 3 commands together in the terminal or do these go elsewhere?
Edit: I'm reading thru Mixpost's docs, and I think I prematurely changed the APP_ENV to production. They have that listed after doing the artisan stuff and when the UI is up. I'll try again tomorrow with a fresh mind. Doing this after work is a horrible idea
-
@humptydumpty do them one at a time and i think you can change it back. I will try a build from scratch tomorrow and go thru the docs to update as needed.
-
@humptydumpty i see it - your DB host is wrong: should be DB_HOST=172.18.30.1
everything else looks correct. -
I changed DB_Host to:
- 172.18.30.1
- 172.18.0.1 (this is the LDAP port for me)
- 172.0.0.1 (this was the default in there originally)
Then, I tried those values for the both fields, DB_Host and for REDIS_HOST just in case they both needed to match.
Same step 7 error. I'm going to start again with a fresh LAMP install.
-
I figured it out. I had to cd into the mixpost-pro-team-app folder before doing step 7.
cd /app/data/mixpost-pro-team-appLine of 1 step 7 went OK. Line 2 with an error. Line 3 went OK.
In Connection.php line 795: SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'job_batches' already exists (Connection: mysql, SQL: create table `job_batches` (`id` varchar(255) not null, `name` varchar(255) not null, `to tal_jobs` int not null, `pending_jobs` int not null, `failed_jobs` int not null, `failed_job_ids` longtext not null, `options` mediumtext null, `cancelled_at` int null, `created_at` int not null, `finished_ at` int null) default character set utf8mb4 collate 'utf8mb4_unicode_ci') In Connection.php line 580: SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'job_batches' already existsStep 10: I nano'd into kernel.php and removed the two references of void, but there's no &. I found actual lines of code in there, so I left those untouched and saved.
Step 11: not sure whether to stay in app/code or cd into /data or the mixpost app folder but running step 11's command shows this:
Reading package lists... Done Building dependency tree... Done Reading state information... Done supervisor is already the newest version (4.2.1-1ubuntu1). W: Not using locking for read only lock file /var/lib/dpkg/lock-frontend W: Not using locking for read only lock file /var/lib/dpkg/lock E: Archives directory /var/cache/apt/archives/partial is missing. - Acquire (2: No such file or directory)Step 12: I encouter an error after running the command
PHP Parse error: syntax error, unexpected token "{" in /app/data/mixpost-pro-team-app/app/Console/Kernel.php on line 14Going to stop here for now.Changed my mind.I changed the environment from local to production. The app is live on my subdomain, despite all the errors. Woohoo!
What does your kernel.php file look like?
-
@humptydumpty remove the ":" at the end of each function and test
-
It's all green.
I am still getting an error on step 11 when installing supervisor.
Reading package lists... Done Building dependency tree... Done Reading state information... Done supervisor is already the newest version (4.2.1-1ubuntu1). W: Not using locking for read only lock file /var/lib/dpkg/lock-frontend W: Not using locking for read only lock file /var/lib/dpkg/lock E: Archives directory /var/cache/apt/archives/partial is missing. - Acquire (2: No such file or directory)But the rest of the steps went smoothly. Now to the real questions:
- What does the upgrade process look like?
- Do Cloudron backups work in case things go south?
-
Nice!!! 🫡
You already have Supervisor it so no need to worry
-
Upgrade process look like?: idk yet as this is new to me too, I'd image its close to the install process. Since we are running off of LAMP and Composer - Mixpost plays nicely. So it should not be too cumbersome* (Famous Last Words, lol)
-
Cloudron backups DO cover whatever is in /app/data/.... in the LMAP app so yeah
You wont be the only one going through the process 🦾
-
-
@privsec Ive updated the docs with @humptydumpty's note on CD'ing to the app dir so just follow the current steps you should be good
-
Hi everyone,
Thank you @plusone-nick for your contribution. I'm glad to see that the community has found a solution to install Mixpost in Cloudron.I have a question, why do we have to delete the voids from the Kernel file?
-
@lao9s Hey Dima,
Thanks!
I recall that I was getting some error with Kernel.php, so I was really just shooting in the dark trying things. It could have been resolved via another change I made, and I was confusing the results.Will have to go back and try to reproduce the error. But assuming I broke or bypassed something with the change, what are the implications?
Edit* Any suggestions/edits on the docs are more than welcome =]
-
@plusone-nick Technically, there should be no error in those functions from Kernel.
I think you had some errors elsewhere and thought this was the solution. If you now have Mixpost functional, try to return ":void" and see if everything is fine.
-
@lao9s Everything is still green
@humptydumpty make the change too
Docs update – Removed the stepDima, I have a question – What happens when using the same pro/enterprise license on two instances? Does the local/production env var enable any test/dev feature?
-
Using the same pro license in production on two or more instances is not allowed.
Using the same enterprise license in two or more instances is allowed and nothing happens.
The
localenv is used when you want to modify the code, usually, the work is done locally. For example: if you have envlocaland want to run a migration, it won't ask you if you are sure to migrate or not, it will simply run the command.
