@CRBear Screenshot of your App Location Settings may help everyone to understand what you have so far, to then help with what you're doing within the LAMP app.

A workaround is to edit the config in the MySQL container: docker exec -ti mysql /bin/bash Then, edit /run/mysql/my.cnf In the container shell itself, supervisorctl restart mysql Note that changes are not persistent across updates (but persists across reboots).

@nebulon I think the problem is consistent, thank you I will contact via email.

@shrey This is interesting. I hadn't noticed before that you had a complete different way of authorization. That's why I made an edit to the post and gave you the exact instruction, which is already implemented as standard.

@girish Thanks, that helped!

Thanks, it works!

@timconsidine said in How to host a website on LAMP?: So Noodl does not require the MondoDB connection ? Noodl is primarily a frontend builder. It's just that it has first-class connectors for Parse (which is based on MongoDB), to add the data layer for your app. Anyway, you can bring any data source (accessible via REST/GRAPHQL/Static) to your app in Noodl.

Ah, thanks, good to know.

@micmc Nice idea, maybe @girish can make it easily configurable with the FileManager (like PHP version) where LAMP/MERN/MEAN is selectable or any combination in between! That would be unique and slick!

https://stackoverflow.com/questions/990392/how-can-i-use-htaccess-rewrite-to-redirect-root-url-to-subdirectory has other ideas as well. If you want /site to appear in the browser URL, you can also do RewriteRule ^$ /site [L] (no trailing slash!)

Thank you so much all, for your suggestion, it solved my problem also.

@girish Thanks for your prompt reply. Ok I will try to contact them to inquire about this. Will keep you guys updated. Best wishes !

Noted. thank you for your responsiveness @girish

@robi this is interesting! I will have a look

Thank you. Did solve my issue. Cheers

@girish said in Unable to access file publicly: @shrey said in Unable to access file publicly: PHP Fatal error: Uncaught Error: Class "Tqdev\PhpCrudApi\Config" not found in The above is the error. There is no such class. Indeed, there's some issue in the code of the api.php itself, which is the main cause. Thanks!

No one in the universe understands how an nginx.conf file works in a LAMP environment - because it doesn't! The syntax in an nginx.conf file is very different from a LAMP - Apache.conf file. One will not work in the other. So, either you are working in a LEMP stack without realizing it, or it isn't an nginx.conf file. https://docs.playtubescript.com/#idocs_start gives some clues, perhaps, of what you are trying to do. Two things I saw in that list that I'm not sure are part of a Cloudron LAMP install is the nodejs config.json file/location, and the ffmpeg item. I don't think either come with the LAMP installation; but this isn't a Cloudron problem per se. No LAMP offering automatically comes with those two items pre-installed and functioning (but the way those two are shown in the image is confusing because it looks like they are IN the root directory of the web server???) It's important to understand that all the talk about Cloudron being so simple and easy is due to the context of Docker. If what you are trying to do has been using Docker, or requires Docker... then Cloudron is the absolute easiest and most powerful option available. If you are managing your web server on it's own server, by hand, then you are able to install whatever, wherever, and make the connections however (although there are typically strict conventions for most software), then Cloudron really isn't necessary. I in fact have a separate VPS on which I just run 3 LAMP php-based apps because there were complications and incompatibilities doing so in a Docker-based LAMP environment. The PHP app you are trying to install clearly assumes a non-Docker, native LAMP environment. On a second reading of the instructions in that link above, I actually suspect you probably followed ALL the steps in the instructions, but you ARE in a LAMP environment, and when you got to the NGINX.CONF section you still followed the instructions... except the webserver isn't using nginx, it is using Apache - so even though you placed the nginx.conf script correctly ("it works"), it isn't being used. And nginx also isn't even running, otherwise you'd get an error message that Apache can't start up because another app is using the required ports. So we are back at @robi's statement - "how is anyone on the forum supposed to know what you are trying to do in the OP?" Next time, include things like the various links I added. And be clearer. I hope you see by this point how unclear your request is! Look over the instructions again, then look carefully at the Cloudron LAMP folder structure - tell us in which folder you put what, for example. Two last things: this PHP app requires a calendar extension which I don't think the Cloudron LAMP app has (https://docs.cloudron.io/apps/lamp/); and finally, the fact it requires PHP 5.5+ suggests it won't even work on the Cloudron LAMP app because that uses, at a minimum, PHP 7.4. And whatever runs on on pre-7.x typically doesn't run on post-7.x. Good luck!

great, it works! thanks https://broadcast.mexina.fr/

@robi said in Allow custom ports: Separate from the ability to manually reconfigure apache after the default install? The container exposes a port, 80 in this case. This 80 is hardcoded as httpPort in the manifest. Thinking more, maybe what you mean is: disable apache altogether, I will run something else on port 80. If this is the case, you are right that manifest does not need to be changed. I don't think we will support this though. It's not a normal flow to install LAMP and then disable apache as first step and run something else. This works for your specific situation only because you don't want a database or expose another port. What if I want postgres? Java? At this point, you will install everything into a data directory and run it from there. This is really not in the spirit of Cloudron.