Skip to forum content
FrontAccounting forum
It's much more fun, when you can discuss your problems with others...
You are not logged in. Please login or register.
Active topics Unanswered topics
Search options
I would like to configure FrontAccounting exclusively from the command line, including adding modules and themes. Once configured, all files in FrontAccounting should be read-only.
I'm currently using FrontAccounting 2.3.24.
The immediate question is: how can I download extensions and themes without going through the FrontAccounting interface?
The background is that I am trying to create a Docker container with FrontAccounting already preconfigured. In Docker, you prepare the files in advance, put them all into its place, and the files are basically immutable from there (there are ways around that, but they defeat the purpose of using Docker in the first place).
I've been to that screen several times, and always overlooked the check box. Thank you!
BTW, I had seen that Wiki entry. That's how I knew that somehow I had to mark an invoice as a template. It only says "...before you can mark it as a template" without going into exactly the detail I needed. And the link to Template Invoice goes to the blank page.
Regardless, thanks for your help!
I'm trying to set up recurring invoices, and am stuck because there are no template invoices. Unfortunately, the template page in the Wiki simply says "To be done".
Apparently, I have to create a regular direct invoice first (which I did), and then somehow mark it as a template.
How do I actually mark an invoice as a template?
My FA version: 2.3.22
I'm logged in as System Administrator and made sure that all permissions are checked.
Thank you for that pointer! It got me started going in the right direction.
Ultimately, the problem turned out to be something different: my proxy configuration inserted the X-Frame-Option DENY into the response headers. Removing that line from my nginx configuration solved the issue.
While I was at it, I also changed the proxy configuration to use HTTP 1.1 instead of 1.0:
proxy_http_version 1.1;
Hint for anybody who may try to track down similar problems: the Firefox plugin Live HTTP Headers was invaluable in solving this mystery.
I am using Frontaccounting 2.3.22. Works beautifully when I access the Web server directly.
I would like to use it behind a reverse proxy (nginx). This seems to work partially, but AJAX calls seem to time out instead of succeed.
Is there any information about how to make such a setup work?
Here is the relevant part of my nginx.conf:
location /accounting {
proxy_pass https://<myinternalserver>:443/accounting;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_redirect off;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
client_max_body_size 8m;
client_body_buffer_size 128k;
proxy_buffering off;
add_header X-Frame-Options DENY;
}
Posts found: 5