-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FreeBSD compatibility #1175
Milestone
Comments
Coming back to the
os.path.join(BASE_DIR, 'static')
|
dennissiemensma
added a commit
that referenced
this issue
Nov 1, 2020
dennissiemensma
added a commit
that referenced
this issue
Nov 1, 2020
Thanks for reporting! I've updated the shebangs and added an env var ( |
Uitgebracht in v4.6 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First of all, thanks for all your work on this neat piece of software!
To increase interoperability over various systems, may I suggest to implement a different shebang for all .sh scripts?
For example, while installing on FreeBSD I had to edit the file:
dsmr-reader/tools/generate-secret-key.sh
Line 1 in 0ee5837
and replace
#!/bin/bash
with#!/usr/bin/env bash
Note: at FreeBSD, bash is not installed by default! use
pkg install bash
Additionally, in
dsmr-reader/dsmrreader/config/production.py
Line 6 in 0ee5837
STATIC_ROOT
is statically defined as '/var/www/dsmrreader/static'. As different systems (and users) have different default and preferred locations for www data, it might be a good idea to be able to set/mention this as override parameter (DJANGO_STATIC_ROOT
) in the .env(.local) file. In my case I had to set it to/usr/local/www/dsmr/dsmr-reader/static
Now, whenever there is an update, I first have to
git reset --hard
, thenpull
, and then re-incorporate above changes.For the setup configuration in FreeBSD, I think people can manage. It deviates a bit from the documentation and example configs (mostly due to different paths), and I myself prefer to use uwsgi in emperor mode.
The text was updated successfully, but these errors were encountered: