Document how to start and update a project in Getting started docs
Add clone-and-drop-.git setup steps and a tag-and-overwrite recipe for updating just novaconium/, mirrored in README.md and /admin/docs/getting-started.
This commit is contained in:
@@ -36,6 +36,30 @@ Visit `http://127.0.0.1:8000/` for the static home page, then click around — `
|
||||
|
||||
Point the vhost's document root at `public/`, make sure `mod_rewrite` is enabled and `AllowOverride All` is set for that directory so `public/.htaccess` takes effect, and it just works — no build step required.
|
||||
|
||||
### Starting a new project
|
||||
|
||||
Clone this repo and drop its Git history — no Composer scaffold or installer:
|
||||
|
||||
```
|
||||
git clone --depth 1 <novaconium-repo-url> my-new-project
|
||||
cd my-new-project
|
||||
rm -rf .git && git init && git add -A && git commit -m "Initial commit from novaconium template"
|
||||
```
|
||||
|
||||
Then replace the example content under `App/pages/` with your own; leave `novaconium/` and `public/` alone.
|
||||
|
||||
### Updating the framework
|
||||
|
||||
Since the framework core lives entirely under `novaconium/`, pick up a new release by overwriting just that directory against a tag and committing the diff:
|
||||
|
||||
```
|
||||
git clone --depth 1 --branch <release-tag> <novaconium-repo-url> /tmp/nova-update
|
||||
rm -rf novaconium && cp -r /tmp/nova-update/novaconium ./novaconium && rm -rf /tmp/nova-update
|
||||
git add novaconium && git commit -m "Update novaconium framework to <release-tag>"
|
||||
```
|
||||
|
||||
Safe by construction — `App/` always overrides `novaconium/`, so an update can't clobber project customizations. See [Getting started](http://127.0.0.1:8000/admin/docs/getting-started) for the full write-up.
|
||||
|
||||
### Add a page
|
||||
|
||||
Create a directory under `App/pages/` with an `index.twig` — the directory path *is* the URL:
|
||||
|
||||
Reference in New Issue
Block a user