Skip to content

Conversation

@TC-MO
Copy link
Contributor

@TC-MO TC-MO commented May 23, 2024

ensure style guide compliance
rewrites for clarity & readability
add admonitions

ensure style guide compliance
rewrites for clarity & readability
add admonitions
@github-actions github-actions bot added the t-docs Issues owned by technical writing team. label May 23, 2024
@TC-MO TC-MO requested review from drobnikj and valekjo May 23, 2024 10:45
@TC-MO
Copy link
Contributor Author

TC-MO commented May 23, 2024

@davidjohnbarton this is now in reviews

Copy link
Member

@drobnikj drobnikj left a comment

Choose a reason for hiding this comment

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

Just idea to keep node version always latest

The following `Dockerfile`:

```dockerfile
FROM apify/actor-node:16
Copy link
Member

Choose a reason for hiding this comment

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

Let's update it to latest node js template with
apify/actor-node:20

Copy link
Member

Choose a reason for hiding this comment

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

Or maybe better remove version and just keep with
apify/actor-node

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Based on proposed changes to dockerfile doc, I will put there apify/actor-node:20 for consistency across docs

```

will build the Actor from the `apify/actor-node:16` image, copy the `package.json` and `package-lock.json` files to the image.
1. Builds the Actor from the `apify/actor-node:16` base image.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
1. Builds the Actor from the `apify/actor-node:16` base image.
1. Builds the Actor from the `apify/actor-node` base image.

Comment on lines 42 to 46
1. Builds the Actor from the `apify/actor-node:16` base image.
2. Copies the `package.json` and `package-lock.json` files to the image.
3. Installs the `npm` packages specified in `packages.json`, omitting development and optional dependencies.
4. Copies the rest of the source code to the image
5. Runs the `npm start` command defined in `package.json`
Copy link
Member

Choose a reason for hiding this comment

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

Question: Maybe it would make more sense to inline this as comments to the Dockerfile?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've slightly restructured the whole doc around this part by:

First providing the whole code block and only after that breaking it up with explanations, @valekjo please let me know if this works better

Copy link
Member

Choose a reason for hiding this comment

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

Nice! Thanks.

restructured the document adding new headings and ToC elements
broke up the code examples for dockerfile and added explanations
@TC-MO
Copy link
Contributor Author

TC-MO commented May 29, 2024

@davidjohnbarton this is now post reviews and will be merged today , tomorrow at the latest

@TC-MO TC-MO merged commit 0432ef0 into master May 30, 2024
@TC-MO TC-MO deleted the development-source-code branch May 30, 2024 11:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-docs Issues owned by technical writing team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants