Add special Deployment instructions for the Mac M1 #263
Conversation
|
Can one of the admins verify this patch? |
14 similar comments
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
| @@ -13,6 +13,13 @@ cd swift-aws-lambda-runtime/Examples/Deployment | |||
|
|
|||
| Note: The example scripts assume you have [jq](https://stedolan.github.io/jq/download/) command line tool installed. | |||
|
|
|||
There was a problem hiding this comment.
This information seems to apply to all types of deployments here (CLI, SAM, Serverless) so I made a special section for it. For an M1 user, this information is really critical.
|
@swift-server-bot test this please |
|
thank you @gestrich |
This adds brief notes on building from an M1 as I don't believe the samples will work without special adjustments.
Motivation:
I had spent a few days attempting to build from my M1 but was a bit confused as to what was wrong. It turned out to be a very simple fix.
Modifications:
Update the Deployment documentation so that M1 users quickly know they need to make some adjustments before spending time trying to deploy the samples.
Result:
Hopefully more users on M1s will be able to deploy the samples.