Before trying to install all the libraries needed (as many/most should already be installed), you should build the app as Linux Arm and run from the command line.
I think there is a way to run the app and get the missing libraries (don’t remember the way to do it but it should be on the Linux section of the forum). Then you can start adding the missing libraries.
Edit: I’m re-reading your post, what version of Xojo are you using?
Lifeboat will install the libraries necessary and has smart detection features so that if you are not using the Barcode class, you do not need to install the Desktop GUI library libgtk.
Every staff member who has worked on the Web 1 framework has eventually said not to use CGI. At one point, the original architect called it a hack. I really can’t say it’s a good idea to use CGI for deployment.
If you are using Xojo 2025r1.1 what do you mean with
?
Do you mean a regular Xojo web server/application?
Is your Linux Arm Server running any other web server?
What errors did you get when you tried to run your Xojo web application?
Are you using Lifeboat to configure your server and install the web app?
My guess is that Ubuntu 24 Linux Arm is 64-bit only.
I don’t think that Xojo 2019 can create 64-bit Arm CGI.
To install CGI you will need a web server (Apache most likely).
Having Apache in your new server will cause you problems when you try to use Xojo 2025 web apps.
Why? I’m not experiencing any problems using Apache with Xojo 2025 web apps
Or I should say I have not run into any specific problems, did I miss an announcement?
I’m sure you have Apache configured in a way to allow this and not the ‘normal’ installation using port 80/443 in conflict with Xojo web apps using the same. Maybe as a reverse proxy?
I’m not sure that OP be able to configure Apache to run old Xojo 2019 CGI and Xojo 2025 standalone applications on Ubuntu Arm.
I have spent the last 5 years developing Lifeboat to use nginx. You will have to search for notes on Apache. I don’t like its config file format and will recommend nginx over Apache any day of the week.
As Tim said, for a Xojo application, Nginx is the preferred way, there’s no advantage in using Apache. Unless you have something very unique, and I guess it’s not the case.
Also as Tim said, he has a tool called Lifeboat tailored to take all that work and complexity from your shoulders. Most things are at few clicks of distance.
Webserver administrator must choose webserver best suited for the planned job, Apache or NGINX (there are others) I hear they can work together but I have not done so.
I would suggest to the OP to purchase @Tim_Parnell Lifeboat and let it do the heavy lifting and configuration. And seeing the great reviews and knowing Tim as top notch coder, it would be the smartest thing to do for sure
As far as a basic Xojo Web setup goes, nginx and Apache do pretty much the same thing. We use these to reverse proxy the user to the web app. I’m not sure if Apache offers a feature that solves the session persistence problem when load balancing, but that is handled by HAProxy with an nginx setup.
I think someone wrote up an Apache guide somewhere here in the forum. I skimmed through the video in the documentation. It is unfortunately outdated and makes heavy reference to Web 1’s CGI builds. The ideas should be the same, but if there are process details they may be outdated or unusable.
