Skip to content
This repository was archived by the owner on Sep 8, 2021. It is now read-only.

Update README.md #16

Closed
wants to merge 1 commit into from
Closed

Update README.md #16

wants to merge 1 commit into from

Conversation

n10000k
Copy link

@n10000k n10000k commented Dec 13, 2018

Updated read me with link to example + small tweaks

Copy link
Member

@txase txase left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR!

I'd like to see it go in a slightly different direction. If the core issue is in how to use extensions, let's fix that section of the readme.

@@ -119,7 +119,7 @@ Hello World! You've reached <?php print($_SERVER['REQUEST_URI']); ?>

You should now have a directory structure like:

```
```yaml
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't yaml. We should leave it as plain text.

@@ -145,10 +145,13 @@ $ sam deploy \
Build the layer by:

1. Installing a Docker environment
1. Running `make`
2. Running `make`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason this is two "1"s is markdown will automatically convert it to a correctly numbered list. The "1" merely signifies that it's a numbered list, not the specific number that will be used when the markdown is rendered. By keeping everything "1" we don't have to fiddle with ensuring the numbers are correct when we insert new steps in the middle of numbered lists.


This will launch a Docker container that will build php71.zip.

Example of installing other php modules:
https://medium.com/@narwy/stackery-php-lambda-layer-add-mysql-1e49f3f3160a
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather expand the documentation in this project than link to somewhere else for helpful instructions. Maybe you could help make the documentation in the extensions section above more clear instead?

@txase
Copy link
Member

txase commented Jan 15, 2019

I'm closing this PR out as there hasn't been any progress on it recently and it needs to be reworked to solve the core issue.

@txase txase closed this Jan 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants