mwa85
commented
7 months ago Hi there a little input here and hope that can help you.
If your are looking for a docker run way there is already your "compact w/external database": This is documented on official Invoiceninja DockerHub: https://hub.docker.com/r/invoiceninja/invoiceninja
Create your key
docker run --rm -it invoiceninja/invoiceninja php artisan key:generate --showRun with your env-variables customized
docker run -d \
-v /var/invoiceninja/public:/var/app/public \
-v /var/invoiceninja/storage:/var/app/storage \
-e APP_ENV='production' \
-e APP_DEBUG=0 \
-e APP_URL='http://ninja.dev' \
-e APP_KEY='<INSERT THE GENERATED APPLICATION KEY HERE>' \
-e APP_CIPHER='AES-256-CBC' \
-e DB_TYPE='mysql' \
-e DB_STRICT='false' \
-e DB_HOST='localhost' \
-e DB_DATABASE='ninja' \
-e DB_USERNAME='ninja' \
-e DB_PASSWORD='ninja' \
-p '80:80' \
invoiceninja/invoiceninjaYou can change the need of volume bind and use docker volume by just customizing the following:
-v /var/invoiceninja/public:/var/app/public \
-v /var/invoiceninja/storage:/var/app/storage \into the following:
-v public:/var/app/public \
-v storage:/var/app/storage \Then having reached a truly one-liner docker run without full CLI / bash access to the server.
If a database is needed within the service then the right way is as it is done today with a compose, there is no reason for IN devs to use time for maintaining a MySQL with the images. Here I have been running InvoiceNinja with docker volumes from a Portainer/Dockage and plain vanilla docker-compose CLI with the need of git clone/pull into my server with existing:
The simple compose requirement:
- docker-compose.yml
- .env
volumes/binds for config and a persistent storages (volume / bind)
- :/var/www/app/public
- :/var/www/app/storage
and for files that are required (pre-created config)
- :/etc/nginx/conf.d/in-vhost.conf:ro
- :/etc/hosts:ro
Here the docker-compose.yml can bee changes to include internal MySQL service or without and then point to external MySQL server, here is an example on how I'm running with docker-compose CLI without the pull (yes I needed to touch and copy config of the "in-vhost.conf" and then the "hosts" files that I have in volume bind on the host).
version: '3.7'
services:
server:
image: nginx
restart: always
env_file: stack.env
volumes:
- ./in-vhost.conf:/etc/nginx/conf.d/in-vhost.conf:ro
- public:/var/www/app/public:ro
depends_on:
- app
ports:
- "80:80"
- "443:443"
networks:
- invoiceninja
- ingress
extra_hosts:
- "in5.localhost:192.168.0.124 " #host and ip
app:
image: invoiceninja/invoiceninja:5
env_file: stack.env
restart: always
volumes:
- ./hosts:/etc/hosts:ro
- public:/var/www/app/public:rw,delegated
- storage:/var/www/app/storage:rw,delegated
networks:
- invoiceninja
extra_hosts:
- "in5.localhost:192.168.0.124 " #host and ip
networks:
invoiceninja:
ingress:
external: true
volumes:
storage:
public:
TomTinking
hillelcoren
daviewales
n1smithy
AlexandreBonneau
I'm looking into invoice ninja and I was really impressed watching some video tutorials on youtube.
However when trying to self host IN I feel like it's to complex and I'm just afraid of the maintenance issues that will arise in the future. I understand the design choices as it allows for redundancy, scaling and flexibility. But as a single person business it's problematic.
What would really work for me is a single container that incorporates everything, something like
invoiceninja/invoiceninja-compact. It would contain the database, invoiceninja itself and the fastcgi reverse proxy with maybe the option to use an external mysql database.This would allow me to incorporate IN in my existing docker compose stack without trying to hack a separate git repo into it.