#django

Anyone know of any good guides for setting up an SMTP server for use with django?

or any application for that matter

patallen: There is nothing related to Django with SMTP.

jtiai: that is why I added 'or any application for that matter'

patallen: Well there are a lot of guides how to setup different SMTP servers, just google for them.

k

And that's something you really normally don't even need to do. Unless you're sysadmin.

(which would mean that you already know what you're doing...)

alright.

I supposed #django wasn't the place to ask for advice on SMTP

thanks anyways

patallen: does it need to accept mail? or just send it?

for send only, there is a great guide on Digital Ocean

I think sending only would do the trick

are we talking about postfix?

The one I mentioned is: https://www.digitalocean.com/community/tutorial...

but they have some guides for other mail servers

that link was exactly what I wanted so I didn't search further

@cnk awesome, thanks

I was hoping to have a server that I could use for mail from several applications... but this looks easy enough to implement

patallen: Another option is docker and premade images.

Hi! Why formset.empty_form is such outdated? Replacing string __prefix__ is not very reliable if such text will be encounered in content. Also manipulating of inline forms via jQuery is cumbersome. There are more suitable libraries for that like knockout.js and angular.

I am having troubles trying to convert these __prefix__ to knockout.js data-bind. I wish it generated proper data-bind out of box.

QuestPC: Err... What is your question?

There is also huge problem that knockout expects all foreach elements to be generated client-side while with inline formsets some might be server-side while another ones added at client-side.

jtiai: formset client-side support is outdated. I found only one mention of using knockout.js with formsets and no code. Trying to implement myself with many obstacles.

QuestPC: How that is "outdated"?

jtiai: Yes that's the tragedy of client-side. Only jQuery is commonly accepted while another libraries are incompatible and no totally accepted one.

QuestPC: Django is totally js library agnostic...

jtiai: Not really admin includes jquery. And there's module that allows manipulating formsets via jQuery but I did not like it.

jtiai: today is not easy to not have anything at client side. Possible but not nice, For example for datetime fields.

QuestPC: I've written several SPA without any problems with Django, mostly using dojotoolkit and extjs...

jtiai: Do you have open-source clientside formset add / delete code? But extjs is superheavy, it's much heavier than angular while knockout.js is small light and fast.

QuestPC: Nope. I work mostly with Restful interfaces. Much more simpler to work than trying to play with dynamic formsets.

jtiai: Yes I wrote such things with ajax-only responses and knockout.js. But there might be problem with web crawlers not indexing such pages. Maybe that's fixed now - I do not know.

jtiai: Also server-side formsets are quite powerful.

I don't know how to explain this, but django-pipeline browserify isn't loading any of my files.

But I'm not seeing any errors.

Hi I’m new to irc and I have a question on how to solve an issue of mine

I’m currently writing a Shopify app with django and I’m trying to use a class as a container for some information

I seem to be getting an error stating that Object is not JSON serializable

lrq: Welcome to #django || Please provide code and __full__ traceback in a pastebin || Pastebin at: http://dpaste.de/ -- do not use pastebin.com!

Here’s the traceback: https://dpaste.de/s1PS and here’s the code: https://dpaste.de/Jiht

lrq: Ok, Django session serializer was changed from pickle to json due security problems. Thus what ever you put in session it must be serializable to json.

So how would I go about making my class serializable to json?

Thanks for the help btw

lrq: Well you have to way to figure you how to convert your class to json or some primitive data like dicts and lists)

lrq: ... that can be serialized as json.

what fields are you trying to serialize?

since I access all of the fields in a different view I guess I have to serialize all of them. Never did anything with serializing before

lrq: Main problem you do have is that you just can't store arbitrary objects to session. You must do something for them that thay may be serialized as json.

Is there another way to store data that doesn’t have to be serialized as json?

lrq: Like first question is, are you absolutely sure that you need all that stuff in session?

I place all of that information in session as I need to access the information in the next view/template

like what?

I kinda have a confirmation page

Have a django-celery question: My tasks seem to have stopped processing, but if I rename them, they work fine.

you do not need a session for that

Why would a task stop working when I restart the application, but if i rename the task and restart the app, it works?

How else should I pass information between views? Global variables I’ve read is a security issue

are*

as POST or GET params

So if I pass the information with POST I don’t need to serialize my class?

POST can only pass strings along

(more or less at least ;))

lrq: what information are you trying to pass around?