mirror of
https://github.com/invoiceninja/dockerfiles.git
synced 2025-12-31 19:47:25 +01:00
Rename files and folders to octane
This commit is contained in:
22
README.md
22
README.md
@@ -1,13 +1,13 @@
|
|||||||
[](https://hub.docker.com/r/invoiceninja/invoiceninja-debian)
|
[](https://hub.docker.com/r/invoiceninja/invoiceninja-octane)
|
||||||
[](https://hub.docker.com/r/invoiceninja/invoiceninja-debian)
|
[](https://hub.docker.com/r/invoiceninja/invoiceninja-octane)
|
||||||
[](https://github.com/invoiceninja/dockerfiles/actions/workflows/publish-image.yaml)
|
[](https://github.com/invoiceninja/dockerfiles/actions/workflows/publish-image.yaml)
|
||||||
[](https://github.com/invoiceninja/dockerfiles/actions/workflows/build-image-v5.yaml)
|
[](https://github.com/invoiceninja/dockerfiles/actions/workflows/build-image-v5.yaml)
|
||||||
|
|
||||||
# Debian Docker for [Invoice Ninja](https://www.invoiceninja.com/)
|
# Octane Docker for [Invoice Ninja](https://www.invoiceninja.com/)
|
||||||
|
|
||||||
:crown: **Features**
|
:crown: **Features**
|
||||||
|
|
||||||
NGINX webserver support [NGINX](https://nginx.org/)
|
[FRANKENPHP](https://frankenphp.dev/)
|
||||||
Built-in Chrome for PDF generation and other features
|
Built-in Chrome for PDF generation and other features
|
||||||
Saxon XLST 2 engine
|
Saxon XLST 2 engine
|
||||||
OPcache
|
OPcache
|
||||||
@@ -18,8 +18,8 @@ Multi language support
|
|||||||
This Debian-based image includes Chrome for enhanced PDF generation and other features. To get started:
|
This Debian-based image includes Chrome for enhanced PDF generation and other features. To get started:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
git clone https://github.com/invoiceninja/dockerfiles.git -b debian
|
git clone https://github.com/invoiceninja/dockerfiles.git -b octane
|
||||||
cd dockerfiles/debian
|
cd dockerfiles/octane
|
||||||
```
|
```
|
||||||
|
|
||||||
Instead of defining our environment variables inside our docker-compose.yml file we now define this in the `.env` file, open this file up and insert your `APP_URL`, `APP_KEY` and update the rest of the variables as required.
|
Instead of defining our environment variables inside our docker-compose.yml file we now define this in the `.env` file, open this file up and insert your `APP_URL`, `APP_KEY` and update the rest of the variables as required.
|
||||||
@@ -51,10 +51,10 @@ The `APP_KEY` can be generated by running:
|
|||||||
|
|
||||||
```bash
|
```bash
|
||||||
# If you haven't started the containers yet:
|
# If you haven't started the containers yet:
|
||||||
docker run --rm -it invoiceninja/invoiceninja-debian php artisan key:generate --show
|
docker run --rm -it invoiceninja/invoiceninja-octane frankenphp php-cli artisan key:generate --show
|
||||||
|
|
||||||
# Or if your containers are already running:
|
# Or if your containers are already running:
|
||||||
docker-compose exec app php artisan key:generate --show
|
docker compose exec app frankenphp php-cli artisan key:generate --show
|
||||||
```
|
```
|
||||||
|
|
||||||
Copy the entire string and insert in the .env file at `APP_KEY=base64....`
|
Copy the entire string and insert in the .env file at `APP_KEY=base64....`
|
||||||
@@ -64,7 +64,7 @@ Copy the entire string and insert in the .env file at `APP_KEY=base64....`
|
|||||||
Start the container with:
|
Start the container with:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
docker-compose up -d
|
docker compose up -d
|
||||||
```
|
```
|
||||||
|
|
||||||
**Note: When performing the setup, the Database host is ```mysql```
|
**Note: When performing the setup, the Database host is ```mysql```
|
||||||
@@ -74,8 +74,8 @@ docker-compose up -d
|
|||||||
To upgrade to a newer release image, update your docker-compose.yml first by running:
|
To upgrade to a newer release image, update your docker-compose.yml first by running:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
docker-compose pull
|
docker compose pull
|
||||||
docker-compose up -d
|
docker compose up -d
|
||||||
```
|
```
|
||||||
|
|
||||||
It is recommended to perform a backup before updating.
|
It is recommended to perform a backup before updating.
|
||||||
|
|||||||
Reference in New Issue
Block a user