Portainer
/
portainer-docs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update create.md 

Hey guys,
I was not too sure if there is a style for writing but I noticed some small errors on the grammatical side. Also noticed some inconsistency when it came to the capitalization of the words "Environment Variables". My major change was the word "won't" as it's really unclear to me if it means wouldn't(conditional) or will not (future tense). I opted for will not but do correct it if it really ought to be the conditional,
pull/184/head
inthelightofthetruth 2021-07-18 12:31:25 -04:00 committed by GitHub
parent cd7188bf44
commit 5da4a7b50f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/v2.0/stacks/create.md
View File

@ -6,7 +6,7 @@ Stacks are collections of services running in a Docker Swarm environment.
You can deploy a new stack from Portainer using the following options:
* Web editor: Using our Web Editor, you will capable to define the services for this stack using a docker-compose format.
* Web editor: Using our Web Editor, you will be able to define the services for this stack using a docker-compose format.
* Upload: If you're already have a stack.yml file, you can upload from your computer to deploy that stack.
* Git Repository: You can use a docker-compose format file hosted in Github.
* Custom Template: If you already created a template of stacks, you can deploy from this option.
@ -25,9 +25,9 @@ When you set up everything, click <b>Deploy the Stack</b>.
### Uploading a stack file
In Portainer, you can create Stacks from compose YML files. To achieve this. Click <b>Stacks</b>, then <b>Add Stack</b>.
In Portainer, you can create Stacks from compose YML files. To achieve this, click <b>Stacks</b>, then <b>Add Stack</b>.
Now <b>Name</b> your new stack, select <b>Upload</b> and choose your compose file from your computer, <b>add environment variables</b> if needed and then click <b>Deploy the Stack</b>.
Now <b>Name</b> your new stack, select <b>Upload</b> and choose your compose file from your computer, <b>add Environment Variables</b> if needed and then click <b>Deploy the Stack</b>.
![create](assets/create-3.png)
@ -43,9 +43,9 @@ If you have your compose file hosted in Github, you can deploy from there. Selec
If you need authenticate, define your user and password. <b>NOTE</b>: If you have a 2FA configured in Github, your passcode is your password.
Set environment variables if needed and then click <b>Deploy the Stack</b>.
Set Environment Variables if needed and then click <b>Deploy the Stack</b>.
The docker-compose.yml file is only pulled once from GitHub for the creation of you stack. After creation, you cannot (auto-)update the stack based on changes in or commits to the file on GitHub. You can make local changes in the <b>Editor</b> tab like for stacks deployed from the <b>Web editor</b> but this won't affect the GitHub hosted file. See for the current status of a feaure request [Add the ability to update and redeploy a stack created from a git repository #1753](https://github.com/portainer/portainer/issues/1753)
The docker-compose.yml file is only pulled once from GitHub for the creation of you stack. After creation, you cannot (auto-)update the stack based on changes in or commits to the file on GitHub. You can make local changes in the <b>Editor</b> tab like for stacks deployed from the <b>Web editor</b> but this will not affect the GitHub hosted file. Check here for the current status of a feaure request: [Add the ability to update and redeploy a stack created from a git repository #1753](https://github.com/portainer/portainer/issues/1753)
![create](assets/create-4.png)