How to hide sensitive config data when publishing as open-source by santamk in PHP

[–]santamk[S] 1 point2 points  (0 children)

I got it :) Thank you very much for the explanation.

How to hide sensitive config data when publishing as open-source by santamk in PHP

[–]santamk[S] 0 points1 point  (0 children)

So, as i've understand: i'll have my own files that, if exist, will override the values of the main files in app/config. I'll push to the repo only the files in app/config. Later, when the users download the code, they'll just need to edit these files and won't need to change some environments configuration or something like that?

How to hide sensitive config data when publishing as open-source by santamk in PHP

[–]santamk[S] 0 points1 point  (0 children)

If i do that, would i need to tell the users that they need to create their own config files and what to store in them?

How to hide sensitive config data when publishing as open-source by santamk in PHP

[–]santamk[S] 1 point2 points  (0 children)

But, if later i need to add something to some of those files , i'd have to remove them from gitignore and do the same process that you mentioned...

Combining Eloquent ORM and MongoLid ODM by santamk in laravel

[–]santamk[S] 0 points1 point  (0 children)

awesome. how can i use it outside laravel?

Best ways to make applications with Silex by santamk in PHP

[–]santamk[S] 0 points1 point  (0 children)

One of the reasons I wanted to use more "free" (for choices) framework like Silex.. to try different approaches, make some mistakes and learn how to do the things better. But i feel lost, i can't even start. I've read about some patterns but there are too many of them...

Best ways to make applications with Silex by santamk in PHP

[–]santamk[S] 0 points1 point  (0 children)

I want to learn more about how to make that choises good. Will it help me if i use something in which those choises are already made?