
Security News
The Changelog Podcast: Practical Steps to Stay Safe on npm
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.
create-aether-cms
Advanced tools
Create Aether CMS projects with no build configuration and seamless update capabilities.
npx create-aether-cms my-cms-site
cd my-cms-site
npm start
Then open http://localhost:8080 to see your site.
When you're ready to deploy to production, create a static build with npm run build.
npx create-aether-cms my-cms-site
Install a specific version, tag, or commit:
# Install specific version
npx create-aether-cms my-blog --version v1.0.0
# Install specific git tag
npx create-aether-cms my-blog --tag stable
# Install specific commit
npx create-aether-cms my-blog --hash abc1234
# Show all available options
npx create-aether-cms --help
# Using npm init
npm init aether-cms my-cms-site
# Using yarn create
yarn create aether-cms my-cms-site
This will create a directory called my-cms-site inside the current folder.
Inside that directory, it will generate the initial project structure and install the dependencies.
my-cms-site/
βββ README.md
βββ node_modules/
βββ package.json
βββ package-lock.json
βββ .gitignore
βββ .gitattributes # β NEW: Conflict-free updates
βββ .env
βββ index.js
βββ core/
β βββ admin/
β βββ api/
β βββ lib/
β βββ routes/
β βββ utils/
βββ assets/
β βββ css/
β βββ js/ # β CONTAINS: New Update utilities
βββ content/
βββ data/
β βββ settings.json # β Enhanced with update preferences
βββ themes/
βββ uploads/
No configuration or complicated folder structures. Just the files you need to build your site.
Using create-aether-cms offers several key benefits:
When you run create-aether-cms, it:
upstream points to the original Aether CMS repo (for updates)origin can be set to your own repository (optional)Your project includes a powerful update system that preserves your customizations while applying upstream improvements.
# Using npm script (recommended)
npm run check-updates
# Using CLI directly
node assets/js/check-updates.js
# Using git directly
git fetch upstream
git log HEAD..upstream/main --oneline # See what's new
# Automated update (preserves your settings)
npm run update-aether
# Manual git approach
git merge upstream/main
# Or apply specific updates
git cherry-pick <commit-hash>
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"
Note: The upstream remote is automatically configured during project creation, so you don't need to add it manually.
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
The update system automatically preserves your customizations:
β Always Protected:
.env)/content/)settings.json).gitignore)β Intelligently Merged:
β οΈ May Require Attention:
| Option | Description | Example |
|---|---|---|
--version | Install specific version tag | --version v1.2.0 |
--tag | Install specific git tag | --tag stable |
--hash | Install specific commit | --hash abc1234 |
Each installation stores metadata for better update management:
{
"aetherCMS": {
"templateName": "aether-cms",
"installedVersion": "v1.0.0",
"installedAt": "2025-01-15T10:30:00.000Z",
"installOptions": {
"version": "v1.0.0",
"tag": null,
"hash": null
}
}
}
During installation, you can optionally connect to your own Git repository:
# During installation, when prompted:
# "Connect to your own Git repository? (y/n): y"
# "Repository URL: https://github.com/YOUR_USERNAME/your-project.git"
# Or add it later:
git remote add origin https://github.com/YOUR_USERNAME/your-project.git
git push -u origin main
The installer automatically configures Git for optimal update handling:
.gitattributes to prevent conflicts on user files# Basic usage
npx create-aether-cms <project-name> [options]
# Options
--version, -v <version> Install specific version (e.g., v1.2.0)
--tag, -t <tag> Install specific git tag (e.g., stable)
--hash, --commit <hash> Install specific commit hash
--help, -h Show help message
# Examples
npx create-aether-cms my-blog
npx create-aether-cms my-blog --version v1.0.0
npx create-aether-cms my-blog --tag stable
npx create-aether-cms my-blog --hash abc1234
If updates fail, the system automatically creates a backup:
# Check available branches
git branch -a
# Restore from backup if needed
git checkout backup-[timestamp]
git checkout main
git reset --hard backup-[timestamp]
# Reset to clean state
git fetch upstream
git reset --hard upstream/main
# Restore your settings
git checkout HEAD~1 -- .env package.json content/data/settings.json
# Re-add upstream remote
git remote add upstream https://github.com/LebCit/aether-cms.git
git fetch upstream
For maximum control, you can also fork the repository:
git clone https://github.com/YOUR_USERNAME/aether-cms.git my-site
cd my-site
git remote add upstream https://github.com/LebCit/aether-cms.git
Create Aether CMS is open source software licensed under the GNU General Public License version 3.0 or later (GPL-3.0-or-later).
See the LICENSE file for full license details.
FAQs
Create Aether CMS projects with no build configuration
The npm package create-aether-cms receives a total of 3 weekly downloads. As such, create-aether-cms popularity was classified as not popular.
We found that create-aether-cms demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago.Β It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.

Security News
Experts push back on new claims about AI-driven ransomware, warning that hype and sponsored research are distorting how the threat is understood.

Security News
Ruby's creator Matz assumes control of RubyGems and Bundler repositories while former maintainers agree to step back and transfer all rights to end the dispute.