Can docker prevent people from accessing source code if I were to put laravel in it?

Read this forum, it's a PHP framework what is there to actually hide.

The right click and view source is not going to show your secrets it's just showing the outputted HTML.

As example, while right here on this page and right click and view source. I don't think you will be able to re-create Jeffrey's site from that.

@jlrdw I'm running it locally. Not hosting. A few cd will see all the controller and model. It's not a problem with front end but as a close source application, I need a way to host locally and hide source code at the same time.

Not to be picky but what would they do with it even if they saw it, anyone good at laravel would not need to copy someone else's Source anyway.

Of course you could have your own login. I don't know what operating system you are using but in Windows you can have separate users with their own logins.

But I didn't realize you was local on this, good luck.

Haven't tried but you could probably package the php into a phar.

The only way someone can view the source code, is if 1) They have access to the server like via ssh or 2) You didn't set your host up properly and /public is not your document root. If /public was your document root, then doing yoursite.com/../ would still not go higher than /public, so they couldn't ever see the source code.

I build interface and backend on laravel and just running it on apache locally on a system. Even though it's localhost, I'm still find a way to protect the .env as the it has password to the main sql server. And the sql server is publicly accessible.

To be simple, Laravel is on lan, SQL server is on the same lan and also public.

Anyway, to hide everything-laravel?

Even in a local set up this guide works and protects the env file

http://novate.co.uk/deploy-laravel-5-on-shared-hosting-from-heart-internet/

I set up laravel both locally and shared using that guide and it works perfect.

You don't have to use .env you know. You can just directly enter the values in the various config files (that are accessing .env) and then delete .env.

@GTHell If you truly want to encrypt it: https://www.sourceguardian.com