What is the point of WordPress (Managed)?
-
@d19dotca said in What is the point of WordPress (Managed)?:
Out of curiosity, what is the difference between WordPress Unmanaged and just installing WordPress inside of the LAMP app?
Until 2-3 releases ago, the main way to get "code" into the LAMP stack was via SFTP (i.e no file manager). We used to get like one support request everyday asking how to install WordPress into LAMP stack because SFTP will fail in many ways (you have to open port 222, people forget sftp:// in filezilla, cloudron SFTP username has two "@" and is sometimes is rejected by clients etc). Our solution was to make a LAMP stack with WP pre-installed, which is essentially Unmanaged WordPress
The other thing Unmanaged WP app has is the WP CLI. It's very useful for automation.
-
Cool - WP CLI is essential for us - good to know.
-
@girish All of this is achievable in LAMP app today though, right? I was able to make a pretty good WordPress install in LAMP yesterday that I could clone from to new domains and it all updated accordingly, mail would send, etc. Just makes me wonder if it's something we can just have those interested in an unmanaged WP do just to keep things "clean" on Cloudron. But maybe that's not desirable by the community, in which is that's fine, just thought I'd suggest it after having tried it with success.
--
Dustin Dauncey
www.d19.ca -
@d19dotca said in What is the point of WordPress (Managed)?:
@girish All of this is achievable in LAMP app today though, right?
Yes, that's correct. Many our LAMP apps are also the same btw, it's not specific to WordPress
For example, say shaarli, invoice ninja, mediawiki, moodle etc. One can just spin up a LAMP stack and install them. It's just a lot of error prone work. As an example, one has to also setup cron jobs in LAMP stack (did you remember to do that for WP?). So, I would say, the benefit is that by specializing packages, you get some of this learnt knowledge automated. -
@girish said in What is the point of WordPress (Managed)?:
@d19dotca said in What is the point of WordPress (Managed)?:
Out of curiosity, what is the difference between WordPress Unmanaged and just installing WordPress inside of the LAMP app?
Until 2-3 releases ago, the main way to get "code" into the LAMP stack was via SFTP (i.e no file manager). We used to get like one support request everyday asking how to install WordPress into LAMP stack because SFTP will fail in many ways (you have to open port 222, people forget sftp:// in filezilla, cloudron SFTP username has two "@" and is sometimes is rejected by clients etc). Our solution was to make a LAMP stack with WP pre-installed, which is essentially Unmanaged WordPress
The other thing Unmanaged WP app has is the WP CLI. It's very useful for automation.
You’re forgetting the minutely Docker cron that you spawn whilst disabling WP’s built in WP-Cron (for good reason, it’s unreliable).
-
@girish That's fair, good point. It's good knowing I can at least run them all in LAMP though if I needed to, my test last night was really just me seeing if I could do it all on my own, haha, then it got me thinking more about the difference between the two.
Curious... any ETA on when the Unmanaged once will come with LDAP? I think that's a highly requested feature for a while now. I know you mentioned before there was a reason to not include it with LDAP when it already had SFTP, but unsure if that's still a current vulnerability or not. If it helps, I could try making the changes needed to implement LDAP by forking the repository if that helps at all.
--
Dustin Dauncey
www.d19.ca -
@Lonk Cool - I feel a new Wordpress (Hyper Edition) coming on
️