fixed heading levels
added blank lines as needed removed trailing spaces added code block for install process removed punctuation from headers
This commit is contained in:
		
							parent
							
								
									a054437bad
								
							
						
					
					
						commit
						a8230eb7f9
					
				| @ -14,33 +14,35 @@ | ||||
| 4. Don't be afraid to submit PR's to the egg repo. | ||||
|     I don't bite. I will work with you on the egg and the required things to run it. | ||||
| 
 | ||||
| ## Step 1. | ||||
| #### Be aware of the pterodactyl install process. | ||||
| ## Step 1 | ||||
| 
 | ||||
| ### Be aware of the pterodactyl install process | ||||
| 
 | ||||
| The Pterodactyl install process is fairly simple once you know. | ||||
| 
 | ||||
| ```md | ||||
|     1. Spin up install container | ||||
|         This uses a volume mount on /mnt/server for the server files. | ||||
|         This can pull or set up all that is needed to run the server. | ||||
|         It is regularly used to just download the files required. Such as server files and configs. | ||||
|          | ||||
|     2. Stop install container | ||||
|      | ||||
|     3. Start a new container with the server files in /home/container | ||||
|         This is where the server is actually run. | ||||
|         Any dependencies installed during the install process are gone. | ||||
|         The container that is started should have everything you need. | ||||
| ``` | ||||
| 
 | ||||
| ## Step 2. | ||||
| #### Testing | ||||
| ## Step 2 | ||||
| 
 | ||||
| ### Testing | ||||
| 
 | ||||
| Make sure your install process is rock solid as I will be testing eggs before they ever hit my repo. | ||||
| 
 | ||||
| I will make suggestions and changes at will. | ||||
| This is to maintain a clean repo that others can pull and be fully aware of what is being done. | ||||
| 
 | ||||
| ## Step 3 | ||||
| 
 | ||||
| ## Step 3. | ||||
| #### Make a branch and do your work in there. | ||||
| ### Make a branch and do your work in there | ||||
| 
 | ||||
| I have been getting messy PR's due to people always PRing from their master branch. Please make a seperate branch and PR from there. | ||||
|  | ||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user