search

jeroennoten / Laravel-AdminLTE

Easy AdminLTE integration with Laravel
MIT License
3.78k stars 1.08k forks source link

[QUESTION] AdminLTE with AWS Cloud9 #1270

Closed carbauma closed 2 months ago

carbauma commented 2 months ago

Hello, I know how to use adminLTD with Visual Studio Code, but when I do the same with Cloud9, it does not work. Can you explain my why?

dfsmania commented 2 months ago

This question will be hard to answer without sharing any details, both Visual Studio Code and AWS Cloud 9 are IDEs, and them should not have any effect on how this package works. An IDE is just a tool (or set of tools) that helps you develop/built your application faster. So, if you have Laravel 7+ working in your IDE, this package should also work there.

carbauma commented 2 months ago

Thank you dfsmania, I know that are just IDEs, but it is strange that I am following the same steps in both IDEs and the problem is only with Cloud9. I have created right now a new environment with cloud9 and then I have installed composer and laravel, finally I have implemented AdminLTD, and when I make a preview, is like it does not show the css styles.

dfsmania commented 2 months ago

@carbauma Use your browser's console, check for errors there, maybe there is some access permission problem in your filesystem, or maybe your Laravel root URL is not correctly configured.

carbauma commented 2 months ago

@dfsmania you are right! I have checked the browser's console, and basically the error is this one:

"Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure stylesheet ''. This request has been blocked; the content must be served over HTTPS."

Do you know what I have to do? thank you!

dfsmania commented 2 months ago

Not really, but looking on the internet may help, for example: https://stackoverflow.com/questions/72289798/laravel-include-css-file-from-mixed-content

It seem you're using an https site, so all content/assets must be requested over https too. I will try setting the ASSET_URL in the environment file, since it's just an environment configuration. That way, you may keep an environment file for http local development and another one for production over https.

carbauma commented 2 months ago

Thank you @dfsmania I have use in the file .env this "ASSET_URL=https://example.com " and is working :)