CoN Source Control: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
#* Include maybe a few sections of CoN with working config. | #* Include maybe a few sections of CoN with working config. | ||
# Set up repository, probably in subversion. | # Set up repository, probably in subversion. | ||
# Add to the repo | # Add to the repo the aforementioned minisite to practice doing things like modification and deployment. | ||
# Split variables out into domain/account specific and general config and var files. | # Split variables out into domain/account specific and general config and var files. | ||
# Consolidate tools and things (wiki, myadmin) onto one domain, probably Grave. | # Consolidate tools and things (wiki, myadmin) onto one domain, probably Grave. | ||
# Set up repository to contain the entire site for real. | # Set up repository to contain the entire site for real. | ||
Revision as of 18:12, 9 August 2013
Tiddles and I would like to get Grave/CoN on source control to make development and deployment easier.
To Do List
First, a list of things we'd need to do.
- Diff the sites and get them as in-sync as possible.
- Create a mini-site based on CoN.
- Include maybe a few sections of CoN with working config.
- Set up repository, probably in subversion.
- Add to the repo the aforementioned minisite to practice doing things like modification and deployment.
- Split variables out into domain/account specific and general config and var files.
- Consolidate tools and things (wiki, myadmin) onto one domain, probably Grave.
- Set up repository to contain the entire site for real.