![]() ![]() I’ve just started using Tailwind actually for scheduling. Used to use VSCO but that got discontinued. I’ve always used Keys to edit my image so I use Pfixer Keys. I know Lightroom’s pretty quick now at culling, but I’ve been using Photo Mechanic for six years now and it’s so intuitive and just simple to use that that’s my go-to. I mean, Photo Mechanic is my go-to for culling. Yeah, there’s definitely a few key bits of software that I use. In future I will show how to get SSL enabled.Are there any pieces of software that you found that you used throughout your processes that you think really help you out? You should now have your own open source invoice solution. The APP_KEY string not being long enough.Database password not matching in the compose file and the environment file.It is also good to read the text that appears in the CLI after you ran docker-compose up. It would be a good idea to re-deploy with APP_DEBUG set to 1 and then you will get an error message in the web interface. If you do not see the Web UI Setup form then something went wrong. The actual data will default to being located under: /var/lib/docker/volumes You can use the docker volume commands to interact with them. You will have seen these at the top of the docker-compose file section like so: volumes: StateĪll state is held in the docker volumes called: If you do not see this screen please refer to the debugging section below. ![]() It would be a good idea to make use of button to send a test email to check your SMTP details are correct. You just need to enter your name details and submit. Most of the details should already be filled in for you (from the environment file earlier). Now navigate to your server's IP or hostname and you should be presented with a form to fill in like below: Now you can deploy with the following command: docker-compose up ![]() I made the env file a non-hidden file so that it is not accidentally forgotten about as it's fairly important as it contains your passwords etc. # - web # uncomment if you want to use external network (reverse proxy for example) Ports: # Delete if you want to use reverse proxy # uncomment if you want to use external network (example network: "web")Įxpose: # Expose ports without publishing them to the host machine - they’ll only be accessible to linked services. You should end up with a docker-compose file that looks like the following: version: '3.6' This will allow the site to be available without needing to enter a port into the URL bar.the database password to match whatever you set in the env file in the previous step.Now go into your docker-compose.yml file and change: The DB_PASSWORD and MYSQL_ROOT_PASSWORD have been updated to a random string and not set to pwd.īy the end of it, you should have something like: docker-compose.yml.E.g should not be: SomeRandomStringSomeRandomString The APP_KEY has been updated to a random string.It is important to ensure the following is the case: You can create a gmail app specific password here.Update the MAIL_ items to your SMTP details.Change the APP_URL to your hostname or IP and remove the :8000.It's very important to change the the following: # Update app db password setting to be the same REPLACE="MYSQL_ROOT_PASSWORD=$DB_PASSWORD" SEARCH="APP_KEY=SomeRandomStringSomeRandomString" MAIL_FROM_NAME="My the following script to set random passwords in the env file: #!/bin/bash MYSQL_DATABASE=ninjaĪPP_URL= APP_KEY=SomeRandomStringSomeRandomString The env file will look like below (unless it has changed since I wrote this tutorial). You should now have a folder called invoice-ninja in your home directory which contains the following files: Mv $HOME/invoice-ninja/src/docker-compose/docker-compose.yml $HOME/invoice-ninja/. Mv $HOME/invoice-ninja/src/docker-compose/nf $HOME/invoice-ninja/nf Mv $HOME/invoice-ninja/src/docker-compose/.env.example $HOME/invoice-ninja/env However, because we will be using a database container, and MySQL has a habbit of growing in memory, I would recommend deploying on a 1GB instance. I managed to deploy on a VM with only 512 MB of RAM. However if you wish to manually deploy it, this guide might be useful. The easiest way to deploy Invoice Ninja is through docker which I will show you below. I will remove this warning message once I have updated this tutorial to work again, but it might contain useful information that still applies. ![]() This post was working when I updated it on the 12th of May 2020, but unfortunately the Invoice Ninja repository has changed since then to the point where this tutorial no longer works. ![]()
0 Comments
Leave a Reply. |