git & Variables

Hey Abdul mannan

Here is a tip https://symfony.com/doc/cur...
You can use both ways described in docs it works perfectly!

Cheers!

Hey Boran,

Sounds not good. Do you mean you did some changes manually in vendor/ directory? If so, that's not the correct way, you should never change directly any third-party code which is inside vendor/ dir - it's totally unsafe to do as you can see. The proper way is to send a PR to the package owner if your changes fix or improve some things, but if you need to make changes related only to your project, you can fork that package, do the changes you need in the fork and then points Composer to your fork with provided fix. If you need more info about it - I can provide a simple example.

But back to your question, if you modify vendor dir (which is very bad as I mentioned) - you're not able to run composer install/update commands anymore. The only way to deploy this broken application is to upload the entire vendor/ directory to the host. But that's a bad idea.

Cheers!

Hi Victor ,

thanks for your Answer , I have modified this code in order to be compatible with the system requirement , not to fix a bug , could you please give me an example how i can avoid that.

Best Regards ,

Hey Boran,

If it might be helpful for others - I think you can suggest your changes to be included in the repo by sending a PR.

What about example, you can tell Composer to look at your fork by specifying URL to your forked repo in composer.json this way:

{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/your-github-nickname/package-name.git"
        }
}

Where "https://github.com/your-github-nickname/package-name.git" is a link to your fork of the repo. In "require" section you need to just tweak the version constraint of this package, the name remains the same, for example, if you push changes to master, than you need to use "dev-master" instead of constraint like "^v1.2.3".

Cheers!

Hey Chris,

If you're wondering about that magical 0775 number - it's a permissions level in Linux OS, where "77" means you allow to read/write/execute for owners and groups, and "5" means you allow to read/execute only for others. So with that task we create a project directory with "755" permissions. If you want more information - read about chmod linux command: https://en.wikipedia.org/wi...

Cheers!

Hey Jian,

Unfortunately, Ansible not able to fill interactive user prompts, that's why we add "--no-interactive" option in some Symfony commands. So you need to handle private repositories in a bit different way, i.e. use SSH key - you can add it in Bitbucket Settings / SSH keys. Also Bitbucket has another cool feature: "Access keys" - in your *repository* settings go to "Access keys" and add one. This access keys provide read-only access to your repository which is perfect for deployment.

Cheers!

well, that is kinda suck. For pulling down bitbucket I can use SSH keys no problem. Think about this situation. In a large enterprise, it is reasonable to ask sysadmins to have different passwords on each node. let's say have different passwords on 1000 nodes. Implementing that would be near impossible. we need a solution to store those keys or password inside Ansible , then when we deploy 1000 nodes we don't need to enter password. when configure server, you need to do alot interactive user prompts for other tasks. Just my thought and I think this is valid question.

Hey Jian,

Ansible has a really great solution for it - the Vault, which helps you to store sensitive data like your DB credentials, passwords, secret tokens, etc. - you will discover it a bit later in this course, check it out here: https://knpuniversity.com/s... . But if we talk about connection to the server - you probably won't use plain passwords. Instead, SSH key is something that you need. And anyway, you need to configure connection to each of 1000 servers if they have different passwords / SSH keys on them.

Cheers!

Hey Victor,
can you do a course on Continuous Integration of a Symfony project with Jenkins ?

Hey Nizar!

Interesting idea! We currently use CircleCI for our continuous integration on SymfonyCasts... and GitHub actions is gaining popularity fast for the same thing (and i use that for many of my open source libraries). These are both "hosted", so they're easier to use than Jenkins (but of course, it will cost you some money). I don't see Jenkins being used nearly as often as it was a few years ago.

Let me know if this helps :).

Cheers!