Update
Updating Your Project
Since your project maintains the original Aether CMS git history and is pre-configured with update capabilities, you can easily update it using git:
# Check what updates are available
git fetch upstream
git log HEAD..upstream/main --oneline # See what's new
# Apply all updates
git merge upstream/main
# Or apply specific updates
git cherry-pick <commit-hash>
Note: The upstream
remote is automatically configured during project creation, so you don't need to add it manually.
If You Need to Re-add the Upstream Remote
If for some reason the upstream remote is missing, you can add it:
# Check existing remotes
git remote -v
# Add upstream if it doesn't exist
git remote add upstream https://github.com/LebCit/aether-cms.git
Safely Updating Your Aether CMS
When updating your Aether CMS instance, your custom content and themes will be preserved as long as you follow these guidelines:
Before Updating
Commit your changes:
git add . git commit -m "Save my changes before update"
Backup your site (optional but recommended):
cp -r my-cms-site my-cms-site-backup
Standard Update Process
# Get the latest updates
git fetch upstream
# View what's changed (optional)
git log HEAD..upstream/main --oneline
# Merge the updates
git merge upstream/main
Safest Update Process (Cherry-picking)
For maximum control, you can selectively apply specific updates:
# View the available updates
git log upstream/main --oneline
# Apply a specific update
git cherry-pick <commit-hash>
Resolve Conflicts
If you've customized core files, you may encounter merge conflicts:
# After running git merge upstream/main
# Edit files to resolve conflicts, then:
git add .
git commit -m "Resolve merge conflicts"
What's Protected During Updates
✅ Always Safe (these are ignored by git):
- Your custom themes in
/content/themes/
(except the default theme) - All your content in
/content/data/
- All your uploads in
/content/uploads/
- Any files listed in
.gitignore
⚠️ May Require Attention:
core
directory unless you're absolutely sure of what you're doing. These files are critical to the system and modifications will create merge conflicts during updates.
- Core files you've modified will show merge conflicts
- You'll need to manually resolve these conflicts
- Changes to the default theme may require attention
After Updating
Install any new dependencies:
npm install # Or npm i
Restart your server:
npm start
Setting Up Your Own Repository
If you want to push your project to your own GitHub repository:
# Create a new repository on GitHub, then:
git remote add origin https://github.com/YOUR_USERNAME/your-project.git
git push -u origin main
Next
You're ready for Aether: The CMS that just works — so you don't have to.