Document the new deployment approach
Also mentioned linkchecker.
This commit is contained in:
		
							parent
							
								
									3069a72763
								
							
						
					
					
						commit
						250db691e4
					
				
					 1 changed files with 9 additions and 7 deletions
				
			
		
							
								
								
									
										16
									
								
								README.md
									
										
									
									
									
								
							
							
						
						
									
										16
									
								
								README.md
									
										
									
									
									
								
							|  | @ -58,12 +58,14 @@ for details. | |||
| 
 | ||||
| ## Deploying | ||||
| 
 | ||||
| Changes pushed to the https://k.sfconservancy.org/website repository are | ||||
| automatically deployed to the production website by the `conservancy-www-update` | ||||
| SystemD timer. See `systemd/conservancy-www-update.timer` for details. | ||||
| To deploy, run `bin/deploy`. This requires SSH access to `hickory.sfconservancy.org`. | ||||
| 
 | ||||
| The `migrate` and `collectstatic` commands are not run automatically. You may | ||||
| need to run these if modifying the database schema or adding/moving static files: | ||||
| 
 | ||||
|     sudo -u www-data /var/www/venv-website/bin/python3 manage.py migrate | ||||
|     sudo -u www-data /var/www/venv-website/bin/python3 manage.py collectstatic --link | ||||
| ## Link checking | ||||
| 
 | ||||
| To check for broken links, log on to `hickory.sfconservancy.org` and run | ||||
| `linkchecker https://sfconservancy.org/`. | ||||
| 
 | ||||
| Note that the Apache configuration has a significant number of aliases and | ||||
| redirects for historic URL changes which means that linkchecker may not run | ||||
| cleanly in local development. | ||||
|  |  | |||
		Loading…
	
	Add table
		
		Reference in a new issue