Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add instructions to deploy for testing purpose #44

Merged
merged 1 commit into from
Feb 23, 2019

Conversation

ikedam
Copy link
Contributor

@ikedam ikedam commented Sep 17, 2018

Hello.
I'm interested in your project, and want to contribute, especially to support #41.

I tried have gitmask run on my environment and update the document adding those instructions.
And I added changes to specify alternate resources (e.g. S3 bucket names, github account, and so on)
with environment variables.
This would make it easier for developers to contribute to gitmask.

* Also adds features to use alternate resource names
|GITHUB_API_TOKEN |github personal access token|
|GITHUB_USER |github username of the personal access token|
|GITMASK_SERVICE |Your own service name for gitmask, e.g. myown-gitmask-api.|
|GITMASK_SERVICE_NORMALIZE|Normalized value for GITMASK_SERVICE,removing special characters and captalize the first letter. e.g. Myowngitmaskapi |
Copy link
Contributor Author

Choose a reason for hiding this comment

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

GITMASK_SERVICE_NORMALIZE is used only in cloudformation-resources.yaml to allow public read for objects in the upload bucket.
I wonder we really need this permission as they are read only by process.js.
I think we can remove cloudformation-resources.yaml and make configurations simpler.

@AnalogJ AnalogJ merged commit 77809f0 into AnalogJ:master Feb 23, 2019
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.

2 participants