Hello everyone a newbie here. Can someone help me install farmos into my cpanel host. I’ve been trying for weeks on my own but still cant get it right.
Welcome to the forum @ibekannfarms! I can’t provide assistance with cpanel specifically because I haven’t used it in a long time myself. But, ultimately I think you will want to use the “packaged release” approach described in the farmOS documentation: Installing farmOS | farmOS
Please note, however, that we may stop producing these “packaged release” tarballs in farmOS v4 (the next version), in favor of encouraging everyone to establish a Composer-based workflow.
See: Building farmOS with Composer | farmOS
A “packaged release” tarball is basically just a “default” farmOS codebase. It’s a nice easy way to drop some code into a webroot and get rolling, but if you plan to use add-on modules then you will want to learn to build your own codebase with your dependencies version controlled so you can avoid incompatibilities or other issues.
Thanks for your responds. Besides cpanel and using Farmier, what other easier ways can someone install FarmOS
I’ll let others chime in if they have developed strategies that work for them and make things easier. Otherwise, I can only recommend the official docs, because I know that they cover everything. I can’t attest to other approaches that I haven’t used.
farmOS is built on Drupal, so it can be installed in any way that Drupal can. Generally speaking if you can install Apache, you can run Drupal/farmOS.
Hosting farmOS has all the same considerations as hosting any web server. I encourage those interested in self hosting to learn and understand the considerations (and risks), how to properly create/restore backups, how to maintain and plan for dependency upgrades, etc.
I don’t want anyone to have a bad experience, and that includes after install when it’s time to upgrade.
We should consider adding a section to that documentation about how to use composer to build your own tarball for deployment in scenarios like this… right now the documentation isn’t very clear that doing so would be an option, but it should work since that’s how we generate the release tarballs currently.
I agree. This is something I would like to prioritize for farmOS v4. We can review/update/merge our hosting docs in a way that makes Composer the recommended workflow for installations that want to use add on modules. I think we can update the Composer documentation generally to show how it can be used to generate a codebase that can be deployed to a shared hosting environment too. Even if the shared hosting environment doesn’t have Composer or provide any CLI tooling, it is still possible to build the code locally, tarball it, and unpack that in the webroot.