Skip to content

Conversation

@travertischio
Copy link

Update the galexie docs for the new helm chart

This PR updates the admin guide for Galexie to take into account the process to install via Helm

@stellar-jenkins
Copy link

@stellar-jenkins
Copy link

@stellar-jenkins
Copy link

## Steps to Configure Galexie

### 1. Copy the Sample Configuration
### Kubernetes
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think need to mention k8s on this page since the page's purpose is mostly runtime environment agnostic and more focused on just config data to network and bucket storage.

Copy link
Author

Choose a reason for hiding this comment

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

cool, what do you think above flipping the structure here and starting with the key config values and then at the bottom having a section just describing copying the config file locally?

#### IAM Role Permissions

### Amazon Web Services (AWS) credentials
When using GCP IAM to authenticate Galexie to access a bucket, the following permissions are required:
Copy link
Contributor

Choose a reason for hiding this comment

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

This may benefit by describing the break out of bucket permissions for the two use cases of Galexie as a Consumer or Publisher. For consumer, the instance just reads from buckets and would only need reduced set of read permissions stated. And then for Publisher, it would be good to mention the extended write permissions needed.

Copy link
Author

Choose a reason for hiding this comment

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

when does Galexie act as a consumer?

@stellar-jenkins
Copy link

2 similar comments
@stellar-jenkins
Copy link

@stellar-jenkins
Copy link

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