Magento 2 changes to pub/.htaccess doesn't reflect

[VivekShingala]

Hi

I am using deployer for a Magento 2 website, and recently I have added some rewrite rules to the pub/.htaccess file and pushed the changes.

However, when I deploy the changes, the original file is being deployed on the server. Has anyone experienced the same issue and has it been resolved already?

[Schrank]

You pushed changes to git and they are not deployed?

This sounds like you have pub/.htaccess in the shared files and therefore you either need to change the deployment, so it is NOT shared or do the changes directly on production in the symlinked file

[VivekShingala]

Hi @Schrank

This file is not part of shared_files and neither it's symlinked.

[Schrank]

But I understood the problem correct?

You change something in git, you push it, you deploy the correct branch/tag and the changes are not there?

[VivekShingala]

yes, that's correct. Previously we're using Deployer Plus and there also we faced the same issue and below was the work around.

set('app_git_checkout_items', ['pub/.htaccess']);

task('app:deploy:git-checkout', function () {
    $activePath = get('deploy_path') . '/' . (test('[ -L {{deploy_path}}/release ]') ? 'release' : 'current');
    foreach (get('app_git_checkout_items', []) as $checkoutItem) {
        run('cd {{release_path}} && git checkout ' . escapeshellarg($checkoutItem));
    }
});

after('deploy:vendors', 'app:deploy:git-checkout');

It was working fine with deployer plus, however, the same task is failing with below error now.

[tmb-staging]  error  in deploy.php on line 66:
[tmb-staging] run cd /mnt/data/home/tmb/public_html/releases/20221223045137 && git checkout 'pub/.htaccess'
[tmb-staging] err fatal: not a git repository (or any parent up to mount point /mnt/data/home)
[tmb-staging] err Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[tmb-staging] exit code 128 (Invalid exit argument)

[Schrank]

In the past deployer checked out the git repository, but today only the code is checked out. There was a ticket I couldn't find which discussed bringing the .git directory back and if I remember correctly a solution for it.

Try running deployer with -vvv so you can check what happens and wether any task is removing/rewriting/changing .htaccess

Beside that, I would check from the beginning and make sure everything is correct:

• You commit the file
• you pushed it
• the change is visible in web git
• you deploy the correct branch
• try git clone with the same command/parameters as deployer in a tmp directory on production to make sure the change is there

Good luck!

[Schrank]

Found it! #2616

[VivekShingala]

Hi @Schrank

Sorry, not getting what to do as there are comments after the issue is closed.

Do I need to refer to this setting update_code_strategy or last comment, which suggests adding the post-receive hook?

[Schrank]

set('update_code_strategy', 'checkout') was the old way which doesn't work anymore.

So I think this should work but I didn't try it:
#2616 (comment)

But maybe it is easier for you to switch back to the old Deployer 6?

I don't think the receive-hook solves your problem. The question in the first place is, what is trying to reset .htaccess?

run cd /mnt/data/home/tmb/public_html/releases/20221223045137 && git checkout 'pub/.htaccess'

[VivekShingala]

I have added a new task app:deploy:git-checkout which is trying to checkout .htaccess file which has some rewrite rules.

Actually, I would like to stick to the latest version, so will not go back to Deployer 6.

[Schrank]

Did you follow the guide above? In theory it should work without your task. If you don't fiddle with .htaccess. In the current Magento 2 recipe isn't anything with .htaccess, that means the file is just replaced during deployment.

The question is: Why isn't it?

-> #3416 (comment)

[peterjaap]

Closing due to inactivity.