This release is a pre-release and may not be stable for production use.
# Django InvoiceProject
This is a Django project aimed at individuals and small businesses that are looking for a simple way to invoice their customers.
This sample project is aimed at a small pet services business, so the models and apps are customized for that use case. Anything can be rewritten to fit other use cases. The invoiceapp relies on Service, Pet, Customer, and Address. As of now, Address is the only published app. It can be installed with pip install django-simple-address (address in INSTALLED_APPS). I do not plan on publishing the services or pets apps as they are very simple and specific to my current use case. I may publish them bundled with the invoiceapp as it is dependent on them.
## Installation
To install the project clone the repository or download the project as a zip and extract it. Change to the django_invoiceproject directory, and install the requirements with pip install -r requirements.txt. Make sure this is done in a virtualenv.
Postfix is used to email customers the invoices.
Make sure that postfix is installed and configured.
For Ubuntu systems: sudo apt-get install postfix will install it.
To configure it: cp /usr/share/postfix/main.cf.debian /etc/postfix/main.cf Add the following lines to main.cf:
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mydestination = localhost
Then, reload this config file: /etc/init.d/postfix reload
For more information checkout the postfix documentation
Test that you can send email from the command line. If this is successfull, you are all done for sending emails
Lastly, configure your postgres database. This project assume that you have created a directory called otm unser /etc/ and created a pass and secret files containing your db user password and your djangi secret key respectively. So, the db user password is under /etc/otm/pass and the secret key is at /etc/otm/secret If you want to change the email host and information, change the configuration in the settings.py file
## Usage
Once all the required packaged are installed in virtualenv and postfix setup Run: python manage.py migrate to create the database tables Then create a superuser: python mange.py createsuperuser, Finally run the development server: python manage.py runserver Then go to localhost:8000/admin. Login with the super user credentials, you should be able to add your business information, and other goodies.
## Contributing
Fork it!
Create your feature branch: git checkout -b my-new-feature
Commit your changes: git commit -am ‘Add some feature’
Push to the branch: git push origin my-new-feature
Submit a pull request :D
## License
Look at the [LICENSE](LICENSE) file at the root of the project
Metadata
Release files for django-invoiceproject 0.1.1a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django_invoiceproject-0.1.1a1.tar.gz | 17.3 kB | Without provenance | Details |
Release files / django_invoiceproject-0.1.1a1.tar.gz
| Download URL | django_invoiceproject-0.1.1a1.tar.gz |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d40c5cdb81c1402b5e573c3a8d9916707abedb6e81001bd3c8c2244827fd68b6
|
|
BLAKE2b-256 checksum How to use checksums |
fb41cf3a846575ca9b3e71ddef97c50092946ce366afd4b5dbb6edcc5ddd0575
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-invoiceproject 0.1.1a1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.