Skip to content

Update content.md - #1966

Open
mcoberly2 wants to merge 1 commit into
docker-library:masterfrom
mcoberly2:patch-1
Open

mcoberly2 wants to merge 1 commit into
docker-library:masterfrom
mcoberly2:patch-1

Conversation

@mcoberly2

Copy link
Copy Markdown
Contributor

Added 2 links & Update other links.

Added 2 links & Update other links.

@tianon tianon left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

👀

(Generally looks fine, but I think you meant to refer to the tags of the repository this description will end up on rather than tags of the other repos you maintain?)

Comment thread aerospike/content.md
### ee-[version]

These tags are for Aerospike EE images, and will require a feature key file, such as the one you get with the single-node EE evaluation, or one associated with a commercial enterprise license agreement.
These [tags](https://hub.docker.com/r/aerospike/aerospike-server-enterprise/tags?page=1&ordering=last_updated) are for Aerospike EE images, and will require a feature key file, such as the one you get with the single-node EE evaluation, or one associated with a commercial enterprise license agreement.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
These [tags](https://hub.docker.com/r/aerospike/aerospike-server-enterprise/tags?page=1&ordering=last_updated) are for Aerospike EE images, and will require a feature key file, such as the one you get with the single-node EE evaluation, or one associated with a commercial enterprise license agreement.
These [tags](https://hub.docker.com/_/aerospike?tab=tags&ordering=last_updated&name=ee-) are for Aerospike EE images, and will require a feature key file, such as the one you get with the single-node EE evaluation, or one associated with a commercial enterprise license agreement.

Comment thread aerospike/content.md
### ce-[version]

These tags are for Aerospike CE images, and do not require a feature key file to start. As mentioned above, the developer API for both is the same, but the editions differ in operational features.
These [tags](https://hub.docker.com/r/aerospike/aerospike-server/tags?page=1&ordering=last_updated) are for Aerospike CE images, and do not require a feature key file to start. As mentioned above, the developer API for both is the same, but the editions differ in operational features.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
These [tags](https://hub.docker.com/r/aerospike/aerospike-server/tags?page=1&ordering=last_updated) are for Aerospike CE images, and do not require a feature key file to start. As mentioned above, the developer API for both is the same, but the editions differ in operational features.
These [tags](https://hub.docker.com/_/aerospike?tab=tags&ordering=last_updated&name=ce-) are for Aerospike CE images, and do not require a feature key file to start. As mentioned above, the developer API for both is the same, but the editions differ in operational features.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@tianon the official repo seems to have reverted to the old docker store publisher. Any changes occurring. We use to update content from updating content.md Have thing changed?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

My guess is that it's probably related to #1899 in some way -- I'll ask again. 😞

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants