ndench
Repos
58
Followers
5
Following
2

An example for how to set up continuous deployment for a Symfony app from CircleCI using Capistrano.

2
1

A quick and dirty tutorial to get you initialised with PHP.

2
0

Ansible role which adds /etc/environment variables

1
0

Ansible role to install mailhog as a systemd service

1
0

Ansible role to install and configure Xdebug

2
0

Events

add docker-compose, firefox-developer and nss-mdns back

stop using handlers for services

configure tlpp

update readme

Created at 22 hours ago

cleanup

Created at 1 day ago

make makefile do git remote

Created at 3 days ago

comment nss-mdns

Created at 3 days ago

comment powertop

Created at 3 days ago

comment firefox-developer and docker-compose

Created at 3 days ago

Revert "remove archlabs-dARK"

This reverts commit 170b8e249b2649b8f782755afe65f12e1c3996be.

comment out archlabs dark and networkmanager

Created at 3 days ago

remove archlabs-dARK

Created at 3 days ago

pacman total download

Created at 3 days ago
FeatureDataCollector should not be registered in kernel debug mode

I haven't found one. Although I'll admit I haven't looked very hard either. I just locked to a previous version.

Created at 1 month ago
Add Ignore Changes Lifecycle to Listener Rules

Unfortunately, the only workaround I've found is to manually define the target groups and listener outside of the module.

So I removed my https_listeners and target_groups from the module:

module "alb" {
  // ...
  
  https_listeners = [
    {
      target_group_index = 0
      // ...
    },
  ]

  target_groups = [
    {
      name = "blue"
      // ...
    },
    {
      name = "green"
      // ...
    }
  ]
  
  // ...
}

And replaced them with manual resources:

resource "aws_lb_target_group" "ecs_blue" {
  name = "blue"

  // ...

  lifecycle {
    create_before_destroy = true
  }
}

resource "aws_lb_target_group" "ecs_green" {
  name        = "green"

  // ...

  lifecycle {
    create_before_destroy = true
  }
}

resource "aws_lb_listener" "https" {
  load_balancer_arn = module.alb.lb_arn

  // ...

  default_action {
    type             = "forward"
    target_group_arn = aws_lb_target_group.ecs_blue.arn
  }

  lifecycle {
    ignore_changes = [default_action]
  }
}

That then allows me to ignore_changes = [default_action]

It would be great if this module could somehow support this. Although, I have no idea how that would work, given the limitations on modules.

Created at 1 month ago
Recommended way to rotate keys

Thanks for the great bundle!

Just looking for someone to point me in the right direction here. In version lcobucci/jwt v4.2.0 a minor BC break was released if you're using a key length of less than 256 bits. This alerted me that I'm actually using key lengths of 248 bits in production. I currently use this bundle to generate magic login tokens for my users.

If I just start using a new key, all the existing login links will be invalidated. Which is not something I want to do (since these particular users cannot generate themselves another link, they receive (relatively) short lived login links from other users).

Do you have a recommended way to rotate keys such that old login links still work correctly (at least for a short period of time)?

Created at 1 month ago
opened issue
Recommended way to rotate keys

Thanks for the great library!

Just looking for someone to point me in the right direction here. In version 4.2.0 an minor BC break was released if you're using a key length of less than 256 bits. This alerted me that I'm actually using key lengths of 248 bits in production. I currently use this library to generate magic login tokens for my users.

If I just start using a new key, all the existing login links will be invalidated. Which is not something I want to do (since these particular users cannot generate themselves another link, they receive (relatively) short lived login links from other users).

Do you have a recommended way to rotate keys such that old login links still work correctly (at least for a short period of time)?

Created at 1 month ago
Errors when creating a service for blue/green deployment

When following the docs for creating an ECS service with blue/green deployments, step 5.2 produces an error. I've successfully completed all the previous steps, but when running the command aws deploy create-deployment-group --cli-input-json file://deployment-group.json I get the following error:

An error occurred (InvalidLoadBalancerInfoException) when calling the CreateDeploymentGroup operation: The specification for load balancing in the deployment group is invalid. The deploymentOption value is set to WITH_TRAFFIC_CONTROL, but either no load balancer was specified in elbInfoList or no target group was specified in targetGroupInfoList.

This seems invalid because we have specifically chosen to not supply either elbInfoList or targetGroupInfoList because they are for classic load balancers and rolling deployments with a single target group.

There appears to be either something missing from the documentation in order for this to work correctly.

Created at 1 month ago
Errors when creating a service for blue/green deployment

Nevermind, turns out I forgot to set the compute platform for the codedeploy application. Very easy to miss in the docs, and the error is not very helpful in this case. This issue (https://github.com/hashicorp/terraform-provider-aws/issues/6802#issuecomment-446340233) helped me track it down.

Created at 1 month ago
Errors when creating a service for blue/green deployment

When following the docs for creating an ECS service with blue/green deployments, step 5.2 produces an error. I've successfully completed all the previous steps, but when running the command aws deploy create-deployment-group --cli-input-json file://deployment-group.json I get the following error:

An error occurred (InvalidLoadBalancerInfoException) when calling the CreateDeploymentGroup operation: The specification for load balancing in the deployment group is invalid. The deploymentOption value is set to WITH_TRAFFIC_CONTROL, but either no load balancer was specified in elbInfoList or no target group was specified in targetGroupInfoList.

This seems invalid because we have specifically chosen to not supply either elbInfoList or targetGroupInfoList because they are for classic load balancers and rolling deployments with a single target group.

There appears to be either something missing from the documentation in order for this to work correctly.

Created at 1 month ago
Git commit message as oneline

Thanks for the great GitHub Action! I was able to get it up and running immediately on the first try!

From the docs I know that we can get the git commit message as ${{ github.event.head_commit.message }}, but I was wondering if there's a way that we can get just the first line of the commit message?

Also, as an FYI, the head_commit.message property only exists on some workflow payloads. You might have to access it differently depending on how the workflow is triggered. Might be worth adding at link to the Workflow Payload doc in the README?

Created at 1 month ago
Git commit message as oneline

Great, thanks for the tip @ravgeetdhillon. For anyone else looking for this, I've managed to get it working with the following. NOTE: I'm triggering the workflow using the workflow_run event, not pull_request.

            - name: Get commit message
              if: always()
              id: commit
              run: echo "::set-output name=message::$(echo '${{ github.event.workflow_run.head_commit.message }}' | head -n 1)"
            - name: Send slack notification
              uses: ravsamhq/notify-slack-action@v2
              if: always()
              with:
                  message_format: '{emoji} ${{ steps.commit.message }}'
                  footer: "<{commit_url}|{repo}> | <{run_url}|{workflow}>"
                  token: ${{ secrets.GITHUB_TOKEN }}
              env:
                  SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

Created at 1 month ago
Git commit message as oneline

Thanks for the great GitHub Action! I was able to get it up and running immediately on the first try!

From the docs I know that we can get the git commit message as ${{ github.event.head_commit.message }}, but I was wondering if there's a way that we can get just the first line of the commit message?

Also, as an FYI, the head_commit.message property only exists on some workflow payloads. You might have to access it differently depending on how the workflow is triggered. Might be worth adding at link to the Workflow Payload doc in the README?

Created at 1 month ago

fix samba

Created at 1 month ago

update power manager

Created at 1 month ago

add workspace 9 and 10

Created at 1 month ago

add ngrok config

Created at 1 month ago
ndench delete branch patch-1
Created at 1 month ago
opened issue
Directories glob patterns broken when used with --git-diff-filter

| Question | Answer | ------------| --------------- | Infection version | 0.26.13 | Test Framework version | PHPUnit 9.5.21 | PHP version | 8.1.18 | Platform | Debian (docker) | Github Repo | -

We run infection only over a specific subset of the codebase which contains heavy business logic. This allows us to enforce a 100% MSI for critical code paths. We do this by using file glob patterns in the directories config section, eg. src/*/Core.

This was recently broken by #1697, specifically by adding the directories configuration to git diff command with escapeshellarg which results in the git diff command being changed to the following, which returns an empty list of changes.

git diff <commit sha> --diff-filter=AM --name-only --  'src/*/Core'

Is there any reason that we need escapeshellarg here? That's usually used to prevent untrusted data being executed, but it should only ever include data provided by the same user who is running the command right?

Alternatively, maybe the directories config property could support regex like excludes does?

<?xml version="1.0" encoding="UTF-8"?>

<!-- https://phpunit.de/manual/current/en/appendixes.configuration.html -->
<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/9.3/phpunit.xsd"
        backupGlobals="false"
        colors="true"
        bootstrap="config/bootstrap.php"
>
   <coverage>
       <include>
           <directory>./src/</directory>
       </include>
   </coverage>
   <php>
       <ini name="error_reporting" value="-1"/>
       <server name="APP_ENV" value="test" force="true"/>
       <server name="SHELL_VERBOSITY" value="-1"/>
   </php>

   <testsuites>
       <testsuite name="All">
           <directory>tests/</directory>
       </testsuite>

       <!-- Different test types you might run separately -->
       <testsuite name="Unit">
           <directory>tests/Unit/</directory>
       </testsuite>
       <testsuite name="Integration">
           <directory>tests/Integration/</directory>
       </testsuite>
       <testsuite name="Message">
           <directory>tests/Message/</directory>
       </testsuite>
       <testsuite name="Contract">
           <directory>tests/Contract/</directory>
       </testsuite>
       <testsuite name="Model">
           <directory>tests/Model</directory>
       </testsuite>
       <testsuite name="Task">
           <directory>tests/Task</directory>
       </testsuite>
       <testsuite name="Functional">
           <directory>tests/Functional/</directory>
       </testsuite>
   </testsuites>
</phpunit>

{
 "timeout": 30,
 "source": {
   "directories": [
     "src/Security",
     "src/*/Core",
     "src/*/Action",
     "src/Integrations/*/Action",
     "src/Integrations/*/Core",
     "src/*/Enum",
   ],
   "excludes": [
     "Migrations"
   ]
 },
 "testFrameworkOptions": "--testsuite=Unit",
 "mutators": {
   "@default": true,
   "IdenticalEqual" : false,
   "NotIdenticalNotEqual": false,
   "MBString": false
 },
 "logs": {
   "text": "build\/infection\/log.txt",
   "debug": "build\/infection\/debug.txt",
   "summary": "build\/infection\/summary.txt"
 }
}

[OK] No files in diff found, skipping mutation analysis.                                                               
Created at 1 month ago

Update links.md (#14)

added an article from doordash and fixed a typo in the line above (into --> intro)

Created at 2 months ago
pull request closed
Update links.md

added an article from doordash and fixed a typo in the line above (into --> intro)

Created at 2 months ago
Doc: Update data.aws_ecs_task_definition arn attribute

Ah, good pickup @justinretzolk. I still have v3.68 so the arn property didn't work for me (it was added in v3.71 from the looks of it). Regardless, I've updated with your suggestion.

Created at 2 months ago

Update website/docs/d/ecs_task_definition.html.markdown

Co-authored-by: Justin Retzolk 44710313+justinretzolk@users.noreply.github.com

Created at 2 months ago