-
Notifications
You must be signed in to change notification settings - Fork 46
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
7 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,8 +23,13 @@ | |
* notification is sent to slack #sparksystemlog with the release name - notifying you that it's ready for deployment | ||
|
||
## Deploying to production | ||
* currently deployment is only possible via ssh, easiest way is using the following command (in Linux): | ||
* `ssh -i spark_production_deployment.id_rsa [email protected] RELEASE_TAG_NAME` | ||
* Assuming you user is authorized (see below how to authorize) | ||
* just type in slack: `/deploy RELEASE_TAG_NAME` | ||
* where RELEASE_NAME is a published github release tag name | ||
* To authorize a user, you will need to ssh to the server and edit the /opt/spark/.env file | ||
* ssh -i spark.id_rsa [email protected] | ||
* `nano /opt/spark/.env` | ||
* look for SLACK_DEPLOY_ALLOWED_USERS - it contains comma-separated list of slack user names allows to deploy | ||
|
||
## See Also | ||
|
||
|