pooperific: The directory that your sqlite DB is in needs to be writeable.
marp has quit
neilus has quit
pooperific
shiet ok, I havent even messed with or setup any sqlite db. wonder where its located
neilus joined the channel
bwbrown
my question is specific to this project but also in general with settings files.
pooperific
so i can probably /alias it in mod wsgi config?
neilus has quit
neilus joined the channel
neilus has quit
neilus joined the channel
Leeds has quit
garygraham joined the channel
neilus_ joined the channel
bsl10 has quit
neilus_ has quit
XofP joined the channel
neilus_ joined the channel
coulix_ joined the channel
bsl10 joined the channel
coulix_ has quit
neilus has quit
neilus_ has quit
neilus joined the channel
bwbrown
or do i just do a setenv for SECRET_KEY?
bsl10 has quit
neilus has quit
garygraham has quit
neilus joined the channel
SimpleName joined the channel
pooperific
mattmcc: hey, so I sudo chown www-data:www-data /var/www/dtuts/dsite1/db.sqlite3, am able to login to my admin panel, but the format is not how its supposed to look
bsl10 joined the channel
its very basic lik html, seems like its missing some styles or something
FunkyBob: i dont know how the hell to config the media and static folders
bsl10 has quit
Utal
I am now using django allauth for registration. Can any one here point me to any link of tutorial which will help me to create my own registration by using inbuilt django auth.
felixx joined the channel
neilus joined the channel
neilus_ has quit
pooperific
FunkyBob: i mean in my wsgi I have alias to my specific apps static folder, dont know how to use collect static
bsl10 joined the channel
FunkyBob: and same thing for media folder, it does not exist in my project
neilus_ joined the channel
bsl10 has quit
neilus has quit
bsl10 joined the channel
neilus_ has quit
neilus joined the channel
neilus has quit
bsl10 has quit
neilus_ joined the channel
omg django config sucks
this is where flask destroys django
bsl10 joined the channel
FunkyBob
?
your web server should be serving your static files
it's all documented in staticfiles and deployment
neilus_ has quit
MEDIA_ROOT is where MEDIA_URL urls will be served from by your web server
neilus joined the channel
STATIC_ROOT is the same for STATIC_URL... and is where "manage.py collectstatic" copies all the static assets into
Utal: do you want "users use email for logn, system sends validation email" approach to registration?
miz- has quit
neilus has quit
pooperific: so, unlike the rest of your project, both STATIC_ROOT and MEDIA_ROOT can liver under your web servers document root
FunkyBob: Yes that what I am trying to do.I am also willing to intregate twillio.
FunkyBob
Utal: whatever that is...
pooperific: how does flask handle static assets?
pooperific: and generated content, for that matter
neilus_ joined the channel
neilus has quit
coulix_ joined the channel
schinckel
twillio is an SMS (and maybe voice) gateway.
FunkyBob
ah, I see
Zequal
Neat.
bsl10 has quit
neilus_ has quit
neilus joined the channel
liothe has quit
bsl10 joined the channel
pooperific
FunkyBob: dont know but ive never had this much headache from trying to serve files holy sht
see heres what i mean, i configured static exactly from django docs
Zequal
pooperific: Django supports local static files. So does Flask. Difference is the Django, in production, encourages you to serve static files via a cdn.
neilus has quit
neilus_ joined the channel
Django is big boy pants, you're dealing with a production level framework out of the box.
Local static files are supported while you develop your app, then you move on to a cdn when you hit production.
neilus_ has quit
neilus joined the channel
You should be doing the same thing in Flask as well, but it doesn't matter so much because Flask apps are a lot smaller and typically don't need all things that come with a larger framework like django.