blob: 835125886f935180c6b29f742dd09b970e0e6bac (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
|
# dispatch-tracker
A slightly older version of this application is still in use for one of
the companies I wrote this for some number of years ago.
Most of the features are here and the application fulfills the use case.
## Things to fix/add going forward:
* More friendly error pages
* Description format field for customer objects &
* on load create page dynamically pull in customer description format
and display above the form field
* Upload Invoice logos on Identity Objects for use in Invoices
* Change Name To "Load Pay System" -- we're going to think about it
* Freight Invoicing System
* Add in an audit log again. ( I ripped it out rather than trying to port it
to Django 3.2 )
## Docker Environment setup
Out of the box you should be able to run:
```shell
$ docker build -t dispatch-tracker:latest .
```
To build a container that will start up a demo version of the application.
This demo container runs:
* Nginx
* uwsgi
* postgresql
The container image has numerous configuration options via environment
variables. Check out the `entrypoint.sh` file for more information on the
specifics there.
With a few tweaks it should be suitable for production deployments, though
you'll want to disable the embedded Postgres database and use a separate server,
ideally with failover.
## To get a development system setup:
It's a pretty straightforward Django application, `requirements.txt` should
point you in the right direction there, `app/settings.py` can be adjusted
to point at whatever database back end you choose via environment variables.
# Misc
Name brainstorming / Use case:
```
Subcontractor invoicing system
Subcontractor Freight Invoicing System
A business solution for subcontractors that don't invoice you.
```
|
