Despite the upgrade issue, additionally the ālegacy flagā is hovering over the Bitnami image. Probably be at least careful and conscious about the decision on whether or not to use this image (especially conscious for production).
Unfortunately, itās marketed as āso easyā, just spin it up and youāre all set.
Thatās only true for temporary testing. In the long run itās a rather bad choice and technically not very feasable.
If someone wants to build up SuiteCRM for the next 3 - 10 years as the backbone and brain of their business, Iād argue itās worth spending some more thoughts and hours on the initial install.
Did I get it wrong or the bitnami images from now on will have to be paid? Meaning you could still get a version of SuiteCRM from their Bitnami Secure Images initiativeā if you pay? And all older images are going legacy?
I didnāt look into this.
But even if that is possible, check how an upgrade, how customizations and how small file changes would work within the image.
I usually argue, that this is a one time thing.
Most customers install the CRM once, use it for a year or years and then look into the upgrade.
The installation here in the forums is just such a big topic, since there are so many different environments and everybody has to go through the installation before getting more quiet again in the forums.
The scripts to automatically install are not strictly required however going from being able to turn on a stack and have everything installed and up and running from pressing go to having to run all the steps manually will cause friction for those who use containers.
We are considering using containers for dev environments. Our Production SCRM server is not containerized. Should we be aware of anything before beginning this endeavor?
youād be building the containers by yourself?
If youāre very familiar with Docker and SuiteCRM installations, it works fairly well.
I usually use a PHP image and adjust it via a Dockerfile and a fairly standard MariaDB container.
For upgrades, Iād still get the files and DB onto a ārealā VM and do everything there, due to the CLI restrictions inside a container (composer / wget / vi etc.)
So far, no good. I gzipād our AWS Linux suitecrm and backed up the db, followed some sketchy instructions from Gemini to create docker images on an ubuntu 24 laptop, and have had so many errors I may have aged 5 years in a day. I get to a login window, but my credentials are not accepted, even after manually resetting the admin hash in the db. Gemini hallucinations abound about how to fix this.
Do you or anyone have a supported or tested way to create a local dev environment on a linux laptop? We are using our production server to test code and it makes me nervous every time I push new code changes.
Iāve got a few installations - usually specifically for customers.
It is more complex than a vanilla Linux LAMP installation and upgrades, customizations, API access, uploads and the new file fields make things more difficult.
Recently, there has been an approach to provide sth. more complete, see whether this helps:
As for the local dev environment:
If you know your way around Linux (Actually, since Suite 8 now isnāt supporting Win server anymore, there is no way around Linux), simply install VirtualBox or virt-manager and install a standard Ubuntu 24 LTS there (no admin UI tools).
The installation is so easy, once the environment is the ācorrect oneā.
That will probably be the APP_SECRET, ensure you have an environment variable set in either .env.local or your docker-compose.yml file that sets APP_SECRET to the value from your main server.
Personally here I use Serversideup, do a pull of (my) current Suite image from Suites download, extract it and use env vars and a startup script to do an install if certain Env vars are not set. Then i have a CLI command that runs the repair/rebuild and cache:clear, it installs all the mysql (if a fresh install) and creates initial user etc. taks about 3 minutes to run..
Just run -