Re: Declarative mechanism for Django model rows

2021-12-09 Thread Carsten Fuchs
Hello,

Am 08.12.21 um 20:25 schrieb Alex Dehnert:
> With some frequency, I end up with models who contents are approximately 
> constant. Are there good ways of handling this?

If I understand your question correctly, you have a model that you always query 
like:

plans = Plan.objects.all()

and that is changed so infrequently that `plans` could be a read-only global, 
updated only on the rare ocassions it is changed in Admin (or shell etc.)? This 
would require to properly encapsulate the writes to the global, about which I 
too (if this covers your question) would be interested in getting help.

Best regards,
Carsten

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/d5c949b7-b6a9-e2bb-b021-eca8786d68d9%40cafu.de.


RE: How to import UGETTEXT_LAZY ON DJANGO 4.0

2021-12-09 Thread ngallen4
Thanks hopefully the same to ugettext

 

Kind Regards

 

Ngallen Ramadhan

T: +255 765 889 960 | Emial:   ngall...@gmail.com | 
Skype: ngallen2

 

From: django-users@googlegroups.com  On Behalf 
Of David Nugent
Sent: 10 December 2021 07:50
To: django-users@googlegroups.com
Subject: Re: How to import UGETTEXT_LAZY ON DJANGO 4.0

 

Simply change it to gettext_lazy. You don't need the deprecated functions, they 
were for python 2.

 

Regards, David

 

On Fri, Dec 10, 2021 at 3:43 PM mailto:ngall...@gmail.com> 
> wrote:

It seems Django has removed ‘ugettext_lazy`(from django.utils.translation 
import ugettext_lazy as _) from Django version 4.0.x

How can I handle translation on Django version 4.0.x?

 

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com 
 .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/009b01d7ed80%246da44d40%2448ece7c0%24%40gmail.com
 

 .

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com 
 .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAE5VhgWHc-1AePPpLKZK5umH00fTrcRsHBefu%2Bb37um-mz%3D3kQ%40mail.gmail.com
 

 .

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/00b801d7ed82%24c6197ed0%24524c7c70%24%40gmail.com.


Re: How to import UGETTEXT_LAZY ON DJANGO 4.0

2021-12-09 Thread David Nugent
Simply change it to gettext_lazy. You don't need the deprecated functions,
they were for python 2.

Regards, David

On Fri, Dec 10, 2021 at 3:43 PM  wrote:

> It seems Django has removed ‘ugettext_lazy`(from django.utils.translation
> import ugettext_lazy as _) from Django version 4.0.x
>
> How can I handle translation on Django version 4.0.x?
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/009b01d7ed80%246da44d40%2448ece7c0%24%40gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAE5VhgWHc-1AePPpLKZK5umH00fTrcRsHBefu%2Bb37um-mz%3D3kQ%40mail.gmail.com.


How to import UGETTEXT_LAZY ON DJANGO 4.0

2021-12-09 Thread ngallen4
It seems Django has removed 'ugettext_lazy`(from django.utils.translation
import ugettext_lazy as _) from Django version 4.0.x

How can I handle translation on Django version 4.0.x?

 

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/009b01d7ed80%246da44d40%2448ece7c0%24%40gmail.com.


Re: django-oscar customisation

2021-12-09 Thread Julio Cojom
You need to fork the app and create a similar protect structure inside your
forked app, then you can start customizing.

Django Oscar isn't an easy way to start with Django



El jue., 9 de diciembre de 2021 8:46 p. m., Ryan Nowakowski <
r...@fattuba.com> escribió:

> Try running the sandbox application:
>
> https://django-oscar.readthedocs.io/en/stable/internals/sandbox.html
>
> Then you can poke around that sandbox code and see how they did things.
>
>
>
> On November 22, 2021 2:23:28 AM CST, "Hervé Edorh" 
> wrote:
>>
>> Hi,
>> I am new to django-oscar and i try to understand the structure of oscar.
>> i have read many times the documentation but i think there is something i
>> don't understand.
>> I fork the template and customise the layout.html, base.html. but how can
>> i build my own first page, i don't see an index.html...
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/A71134F3-1FAA-4759-AF4C-E3887F45E1CC%40fattuba.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAHRQUHkMS9JkmHR0RVRWi230WVZDj%2BYYoh_MgJ98BnVQd-AJ%3DQ%40mail.gmail.com.


Re: django-oscar customisation

2021-12-09 Thread Ryan Nowakowski
Try running the sandbox application:

https://django-oscar.readthedocs.io/en/stable/internals/sandbox.html

Then you can poke around that sandbox code and see how they did things.



On November 22, 2021 2:23:28 AM CST, "Hervé Edorh"  wrote:
>Hi, 
>I am new to django-oscar and i try to understand the structure of oscar. i 
>have read many times the documentation but i think there is something i 
>don't understand.
>I fork the template and customise the layout.html, base.html. but how can i 
>build my own first page, i don't see an index.html...
>
>-- 
>You received this message because you are subscribed to the Google Groups 
>"Django users" group.
>To unsubscribe from this group and stop receiving emails from it, send an 
>email to django-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit 
>https://groups.google.com/d/msgid/django-users/4000707d-c14e-4193-92b8-730a4d2aa5den%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/A71134F3-1FAA-4759-AF4C-E3887F45E1CC%40fattuba.com.


Re: Declarative mechanism for Django model rows

2021-12-09 Thread Ryan Nowakowski
Check out fixtures:

https://docs.djangoproject.com/en/3.2/howto/initial-data/

On December 8, 2021 1:25:45 PM CST, Alex Dehnert  wrote:
>With some frequency, I end up with models who contents are approximately 
>constant. Are there good ways of handling this?
>
>For example, I might have a set of plans that users can sign up 
>for, with various attributes -- ID, name, order in the list of plans, 
>cost, whether the purchaser needs to be a student/FOSS project/etc.. I'm 
>going to rarely add/remove/change rows, and when I do there's likely going 
>to be code changes too (eg, to change landing pages), so I'd like the 
>contents of the model (not just the schema) to be managed in the code 
>rather than through the Django admin (and consequently use pull requests 
>to manage them, make sure test deploys are in sync, etc.). I'd also like 
>it to be in the database, though, so I can select them using any column of 
>the model, filter for things like "show me any project owned by a paid 
>account", etc..
>
>I think my ideal would be something like "have a list of model instances 
>in my code, and either Django's ORM magically pretends they're actually in 
>the database, or makemigrations makes data migrations for me", but I don't 
>think that exists?
>
>The two workable approaches that come to mind are to either write data 
>migrations by hand or use regular classes (or dicts) and write whatever 
>getters and filters I actually want by hand.
>
>Data migrations give me all the Django ORM functionality I might want, but 
>any time I change a row I need to write a migration by hand, and figuring 
>out the actual state involves either looking in the Django admin or 
>looking through all the data migrations to figure out their combined 
>impact. (Oh, and if somebody accidentally deletes the objects in the 
>database (most likely on a test install...) or a migration is screwy 
>recovering will be a mess.)
>
>Just using non-ORM classes in the source is a clearer, more declarative 
>approach, but I need to add replacements for many things I might normally 
>do in the ORM (.objects.get(...), __plan__is_student, 
>.values(plan__is_student).annotate(...), etc.).
>
>Which of these approaches is better presumably depends on how much ORM 
>functionality I actually want and how often I expect to be changing 
>things.
>
>Are there other good approaches for this? Am I missing some Django feature 
>(or add-on) that makes this easier?
>
>Thanks,
>Alex
>
>P.S. I previously asked this on StackOverflow at 
>https://stackoverflow.com/questions/70204467/declarative-mechanism-for-django-model-rows,
> 
>but I'm realising this list is probably better.
>
>-- 
>You received this message because you are subscribed to the Google Groups 
>"Django users" group.
>To unsubscribe from this group and stop receiving emails from it, send an 
>email to django-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit 
>https://groups.google.com/d/msgid/django-users/alpine.DEB.2.21.2112081409120.12786%40novgorod.mit.edu.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/55D126DC-6D7A-42EE-A482-423C214E7677%40fattuba.com.


Database "InterfaceError connection already closed" with asgi.

2021-12-09 Thread peter.wagemans via Django users

Database "InterfaceError connection already closed" with asgi.


This often seems to happen when an exception was triggered, e.g., even
a simple Http404 due to incorrect URL.

A suspicion is discussed below. Ideas about this suspicion, how to
validate it and how to avoid the problem will be appreciated.

Note the following in django/core/handlers/exception.py:

response = await sync_to_async(response_for_exception, 
thread_sensitive=False)(request, exc)

The "Asynchronous support" page:

  https://docs.djangoproject.com/en/3.1/topics/async/

thread_sensitive=False: the sync function will run in a brand new
thread which is then closed once the invocation completes.

We have an application (currently at Django 3.1.6) with a base
template that includes a banner with messages for users. It uses the
ORM to fetch the messages (if any) from the database. That base
template is also used for custom exception pages (e.g., handler404).
This appears to bite us in response_for_exception if it gets executed
in a different thread with a problematic database connection.

In several places Django uses sync_to_async with
thread_sensitive=True.  That is now also the default value (new True
in 3.1 vs old False in 3.0).

  https://docs.djangoproject.com/en/3.1/topics/async/ says:

Warning

asgiref version 3.3.0 changed the default value of the
thread_sensitive parameter to True. This is a safer default, and
in many cases interacting with Django the correct value, but be
sure to evaluate uses of sync_to_async() if updating asgiref from
a prior version.

So, shouldn't True be used in the above response_for_exception calls
as well, to allow safe use of the ORM in exception response
processing?

Similar reasoning may apply to django/contrib/staticfiles/handlers.py:

return await sync_to_async(response_for_exception, 
thread_sensitive=False)(request, e)

Thanks.


-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/AM9PR01MB7412BF3787F063F2180097AA9D709%40AM9PR01MB7412.eurprd01.prod.exchangelabs.com.


Re: AttributeError: 'Values' object has no attribute 'link_base' in building sphinx documentation.

2021-12-09 Thread Jason
you could raise a bug report on the django tracker 
at https://code.djangoproject.com/query but I'm doubtful that this will 
gain any traction

Those versions of django you specified are very out of date.  1.10 was EOL 
in 2017, 1.11 EOL'd April 2020 and 2.0 EOLd Aug 2018

If you don't have any issues with currently supported versions (2.2, 3.2 
and 4.0),  then its likely that any PRs won't be applied. 

On Thursday, December 9, 2021 at 10:15:03 AM UTC-5 sencer...@gmail.com 
wrote:

> Hello everyone,
>
> If 'sphinx.ext.autodoc' extension enabled in conf.py of sphinx, when I try 
> to run 'make html' I'm ending up with AttributeError exception:
>
> Exception occurred:
>   File 
> /env/lib/python3.6/site-packages/django/contrib/admindocs/utils.py", line 
> 121, in _role
> inliner.document.settings.link_base,
> AttributeError: 'Values' object has no attribute 'link_base'
>
> I tried it with combinations of some django and sphinx versions.
>
> Here is the no luck list:
> django 1.10, django 1.11 and sphinx 3.5
> django 2.0.13 and sphinx 3.5 , sphinx 4.0, sphinx 4.2.0, sphinx 4.3.1
>
> I also opened an issue at sphinx github but they said this has to do with 
> django admindocs instead of  sphinx.
>
> Is there anybody who has resolved the AttributeError exception thrown 
> while building documents via sphinx?
>
> Regards,
> Sencer HAMARAT
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/d684ad8e-3001-4d36-8b13-33ce0029cb32n%40googlegroups.com.


AttributeError: 'Values' object has no attribute 'link_base' in building sphinx documentation.

2021-12-09 Thread Sencer Hamarat
Hello everyone,

If 'sphinx.ext.autodoc' extension enabled in conf.py of sphinx, when I try
to run 'make html' I'm ending up with AttributeError exception:

Exception occurred:
  File /env/lib/python3.6/site-packages/django/contrib/admindocs/utils.py",
line 121, in _role
inliner.document.settings.link_base,
AttributeError: 'Values' object has no attribute 'link_base'

I tried it with combinations of some django and sphinx versions.

Here is the no luck list:
django 1.10, django 1.11 and sphinx 3.5
django 2.0.13 and sphinx 3.5 , sphinx 4.0, sphinx 4.2.0, sphinx 4.3.1

I also opened an issue at sphinx github but they said this has to do with
django admindocs instead of  sphinx.

Is there anybody who has resolved the AttributeError exception thrown while
building documents via sphinx?

Regards,
Sencer HAMARAT

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CACp8TZgkaogKXkfonu%3DacRwfN%3D_yG5UzW85i1BSAThR-H0qCZA%40mail.gmail.com.


Deploy to production django + channels

2021-12-09 Thread Gustavo Bazan
Hi, I have a django project that has the following services

django, celery, celery beats, channels, nginx (everything works with docker)

My question is the following, when deploying in production, is it necessary 
to set up two different servers for django and channels? or can it be done 
only with uvicorn/daphne and django's ASGI config?


*Option 1*
Deploy only with daphne
In nginx both, django and channels point to the same server
daphne -b 0.0.0.0 -p 8000 config.asgi: application

*Option 2*
Deploy django and channels separately
In nginx, django and channels have separate servers

- For django
/ usr / local / bin / gunicorn config.asgi: application -k 
uvicorn.workers.UvicornWorker --bind 0.0.0.0:8080 --chdir = / app

- For channels
daphne -b 0.0.0.0 -p 8000 config.asgi: application


Previously when django use only WSGI, it was necessary to run both services 
separately. But now I have doubts since django can use ASGI directly.


Also, does anyone have any experience regarding the performance of using 
daphne, uvicorn or some other server?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/acc06f59-1a32-4554-8010-699b071afb37n%40googlegroups.com.


Re: Why does sqlmigrate need a connection to an existing database?

2021-12-09 Thread Jason
It uses db connection in two places:

building the migration graph 

 in 
order to load previous applied migrations and transaction begin/end wrapping 


This makes sense, because you can have N unapplied migrations between the 
db and your migrations history package.  



On Tuesday, December 7, 2021 at 7:46:42 PM UTC-5 shmuel@partnerize.com 
wrote:

> Wondering why sqlmigrate needs a connection to an existing database.
>
> I understand that for certain commands, it needs the database to generate 
> the migration. But for most (basic) commands, no connection is really 
> needed.
>
> For example, I created a test project 
> and
>  
> generated migration files. Without ever running the `migrate` command, I 
> was able to use `sqlmigrate` perfectly well on all migrations, save the 
> last, which drops a `unique_together`.
>
> I'm sure there are other commands which actually need a database 
> connection (though I haven't found them yet). Seems to me sqlmigrate could 
> be rewritten along the lines of:
>
>- Try to generate sql from migration file
>- If it hits a command it needs the database, attempt to connect
>
> Or else:
>
>- If no connection, check if migration file needs connection to 
>database
>
> Is there something I'm unaware of?
>
>
> This email may contain confidential material; unintended recipients must 
> not disseminate, use, or act upon any information in it. If you received 
> this email in error, please contact the sender and permanently delete the 
> email.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/769abf5f-8afe-4801-8355-fbf27c5b301bn%40googlegroups.com.


Re: Why does django throw TypeError when sending requests through Apache WSGI?

2021-12-09 Thread Jason

with your settings usage, are you defining a property in settings and 
trying to use it anywhere?

furthermore, are you using settings via 

from traveldata.traveldata import settings (example)

or via

from django.conf import settings

The latter is the recommended means because settings are lazy loaded.
On Wednesday, December 8, 2021 at 10:07:11 AM UTC-5 sencer...@gmail.com 
wrote:

> Hi,
>
> I think this is not related with apache
>
> It seems like class object property is called as a method somehow.
> Unfortunately the error does not reveal the property name.
>
> Regards,
> Sencer HAMARAT
>
>
>
> On Wed, Dec 8, 2021 at 4:59 PM Kyle Paterson  wrote:
>
>> Started a new project after not using Django for roughly two years, works 
>> fine when running as a development server but throws TypeError: 
>> SimpleLazyObject class: property object not callable.
>>
>> From apache error log:
>> [Wed Dec 08 10:11:53.023239 2021] [wsgi:error] [pid 10704:tid 
>> 140343150348032] [remote 127.0.0.1:44946] Traceback (most recent call 
>> last):
>> [Wed Dec 08 10:11:53.023283 2021] [wsgi:error] [pid 10704:tid 
>> 140343150348032] [remote 127.0.0.1:44946]   File 
>> "/home/kyle/active-travel/traveldata/traveldata/wsgi.py", line 14, in 
>> 
>> [Wed Dec 08 10:11:53.023327 2021] [wsgi:error] [pid 10704:tid 
>> 140343150348032] [remote 127.0.0.1:44946] from django.core.wsgi 
>> import get_wsgi_application
>> [Wed Dec 08 10:11:53.023351 2021] [wsgi:error] [pid 10704:tid 
>> 140343150348032] [remote 127.0.0.1:44946]   File 
>> "home/kyle/active-travel/venv/lib/python3.8/site-packages/django/__init__.py",
>>  
>> line 1, in 
>> [Wed Dec 08 10:11:53.023371 2021] [wsgi:error] [pid 10704:tid 
>> 140343150348032] [remote 127.0.0.1:44946] from django.utils.version 
>> import get_version
>> [Wed Dec 08 10:11:53.023377 2021] [wsgi:error] [pid 10704:tid 
>> 140343150348032] [remote 127.0.0.1:44946]   File 
>> "home/kyle/active-travel/venv/lib/python3.8/site-packages/django/utils/version.py",
>>  
>> line 7, in 
>> [Wed Dec 08 10:11:53.023430 2021] [wsgi:error] [pid 10704:tid 
>> 140343150348032] [remote 127.0.0.1:44946] from 
>> django.utils.regex_helper import _lazy_re_compile
>> [Wed Dec 08 10:11:53.023435 2021] [wsgi:error] [pid 10704:tid 
>> 140343150348032] [remote 127.0.0.1:44946]   File 
>> "home/kyle/active-travel/venv/lib/python3.8/site-packages/django/utils/regex_helper.py",
>>  
>> line 10, in 
>> [Wed Dec 08 10:11:53.023524 2021] [wsgi:error] [pid 10704:tid 
>> 140343150348032] [remote 127.0.0.1:44946] from 
>> django.utils.functional import SimpleLazyObject
>> [Wed Dec 08 10:11:53.023529 2021] [wsgi:error] [pid 10704:tid 
>> 140343150348032] [remote 127.0.0.1:44946]   File 
>> "home/kyle/active-travel/venv/lib/python3.8/site-packages/django/utils/functional.py",
>>  
>> line 364, in 
>> [Wed Dec 08 10:11:53.023578 2021] [wsgi:error] [pid 10704:tid 
>> 140343150348032] [remote 127.0.0.1:44946] class 
>> SimpleLazyObject(LazyObject):
>> [Wed Dec 08 10:11:53.023611 2021] [wsgi:error] [pid 10704:tid 
>> 140343150348032] [remote 127.0.0.1:44946] TypeError: Error when calling 
>> the metaclass bases
>> [Wed Dec 08 10:11:53.023613 2021] [wsgi:error] [pid 10704:tid 
>> 140343150348032] [remote 127.0.0.1:44946] 'property' object is not 
>> callable
>>
>> Apache site config file:
>> 
>> # The ServerName directive sets the request scheme, hostname and 
>> port that
>> # the server uses to identify itself. This is used when creating
>> # redirection URLs. In the context of virtual hosts, the 
>> ServerName
>> # specifies what hostname must appear in the request's Host: 
>> header to
>> # match this virtual host. For the default virtual host (this 
>> file) this
>> # value is not decisive as it is used as a last resort host 
>> regardless.
>> # However, you must set it for any further virtual host 
>> explicitly.
>> #ServerName www.example.com
>>
>> ServerAdmin webmaster@localhost
>> 
>> Alias /static /home/kyle/active-travel/traveldata/static
>> 
>> Require all granted
>> 
>>
>> 
>> 
>> Require all granted
>> 
>> 
>>
>> WSGIScriptAlias / 
>> /home/kyle/active-travel/traveldata/traveldata/wsgi.py 
>> process-group=traveldata
>> WSGIDaemonProcess traveldata 
>> python-home=/home/kyle/active-travel/venv 
>> python-path=/home/kyle/active-travel/traveldata/traveldata
>> WSGIProcessGroup traveldata
>>
>> # Available loglevels: trace8, ..., trace1, debug, info, notice, 
>> warn,
>> # error, crit, alert, emerg.
>> # It is also possible to configure the loglevel for particular
>> # modules, e.g.
>> #LogLevel info ssl:warn
>> LogLevel info
>>
>> ErrorLog ${APACHE_LOG_DIR}/error.log
>> CustomLog ${APACHE_LOG_DIR}/access.log