Update README.md
parent
bc14d19206
commit
54cc9319e4
98
README.md
98
README.md
|
|
@ -1 +1,97 @@
|
|||
# indymedia.org
|
||||
## indymedia
|
||||
|
||||
**Independent Media Center** – a ready‑to‑run WordPress codebase that recreates the archived [indymedia.org](https://web.archive.org/web/*/indymedia.org) hub.
|
||||
The stack runs inside Docker and pulls all required plugins via Composer.
|
||||
|
||||
---
|
||||
|
||||
### Quick start – get it running in three steps
|
||||
|
||||
1. **Clone the repository**
|
||||
|
||||
```bash
|
||||
git clone https://github.com/RadioParalelo/indymedia.org.git indymedia-wp
|
||||
cd indymedia-wp
|
||||
```
|
||||
|
||||
2. **Build the Docker image**
|
||||
|
||||
```bash
|
||||
docker build -t indymedia:test .
|
||||
```
|
||||
|
||||
3. **Start the container**
|
||||
|
||||
```bash
|
||||
docker run -d \
|
||||
--name indymedia \
|
||||
-p 8080:80 \
|
||||
-v "$(pwd)/wp-data:/var/www/html/wp-content" \
|
||||
indymedia:test
|
||||
```
|
||||
|
||||
Then open **http://localhost:8080/wp-admin** in a browser, run the WordPress installer, and activate the plugins you need.
|
||||
|
||||
---
|
||||
|
||||
### What the project contains
|
||||
|
||||
| Component | Description |
|
||||
|-----------|-------------|
|
||||
| **Dockerfile** | Builds a clean `wordpress:php8.2-apache` image, installs Composer, WP‑CLI, and copies your custom theme. |
|
||||
| **composer.json / composer.lock** | Lists the 18 plugins (WPackagist mirror) that are installed into `wp-content/plugins/`. |
|
||||
| **indy‑wp/indywp/** | Your custom theme (built and ready to use). |
|
||||
| **config/php.ini** | Optional PHP tweaks (upload limits, memory, etc.). |
|
||||
| **docker‑compose.yml** *(optional)* | Example compose file for a full stack (MySQL, phpMyAdmin, etc.). |
|
||||
| **README.md** | This file. |
|
||||
|
||||
---
|
||||
|
||||
### Installing the plugins
|
||||
|
||||
After the container is running, open the WordPress admin, go to **Plugins → Installed Plugins**, and click **Activate** for each plugin you want.
|
||||
All plugins are already present in `wp-content/plugins/` thanks to `composer install` that runs during the image build.
|
||||
|
||||
---
|
||||
|
||||
### Adding or updating plugins
|
||||
|
||||
1. Edit `composer.json` – add or change a package from WPackagist, e.g.:
|
||||
|
||||
```json
|
||||
"require": {
|
||||
"wpackagist-plugin/wp-super-cache": "^2.0",
|
||||
"wpackagist-plugin/new-plugin": "^1.2"
|
||||
}
|
||||
```
|
||||
|
||||
2. Re‑build the image (step 2 above).
|
||||
Composer will fetch the new versions and place them in the image.
|
||||
|
||||
---
|
||||
|
||||
### Custom mu‑plugins
|
||||
|
||||
If you have PHP files that must always run (e.g., security hardening), place them in the local `src/` directory before building.
|
||||
Docker copies everything from `src/` into `wp-content/mu-plugins/`, and WordPress loads them automatically—no activation required.
|
||||
|
||||
---
|
||||
|
||||
### License
|
||||
|
||||
The core theme is **Twenty Twenty‑Five**, licensed under **GPL v2 or later**.
|
||||
All other code in this repository is also distributed under the GPL v2+ (see individual plugin licenses).
|
||||
|
||||
---
|
||||
|
||||
### Contributing
|
||||
|
||||
1. Fork the repo.
|
||||
2. Make your changes (code, docs, plugin list, etc.).
|
||||
3. Submit a pull request.
|
||||
|
||||
All contributions are accepted under the same GPL license.
|
||||
|
||||
---
|
||||
|
||||
*For deeper developer notes, see the `docs/` folder.*
|
||||
|
|
|
|||
Loading…
Reference in New Issue