Hi,
I did some more testing -> uploads in a work just fine; it seems to go
wrong with our automatic thumbnailing stuff.
The thumbs were saved on disk (static/thumbnails) via a compute lambda
construction.
Field('logo','upload', requires=IS_IMAGE(), label=T('Members logo')),
Field('logo_thumb_159', 'upload', compute=lambda r: THUMB(r['logo'], 159,
101, True)),
I think I need to rewrite the THUMB code to store the thumb in de DB.
I can also confirm that the migration stuff works fine. (after doing a one
time fake_migrate_all).
Thanks :)
Kind Regards Rene
On Wednesday, June 18, 2014 1:11:25 AM UTC+2, Derek wrote:
>
> - using an already existing DB; while being able to support future
> migrations
>
> just fake_migrate_all and then remove that line. regular migrations should
> work. If not, send your sql.log.
>
> what's your issue with file uploads? do they work locally and fail on
> hosted?
>
> On Tuesday, June 17, 2014 7:27:25 AM UTC-7, Rene Dohmen wrote:
>>
>> Hi,
>>
>> Are the any users at all using heroku and web2py with a postgres DB?
>>
>> The demo app:
>> http://tranquil-spire-8889.herokuapp.com/
>>
>> We are running into problems also for:
>> - file uploads
>> - using an already existing DB; while being able to support future
>> migrations
>>
>> Kind Regards,
>>
>> Rene
>>
>> On Friday, June 13, 2014 4:14:49 PM UTC+2, Rene Dohmen wrote:
>>>
>>> Hi Web2py Users,
>>>
>>> I deployed an app with postgres on Heroku following the info in:
>>>
>>>
>>> https://github.com/web2py/web2py/blob/master/scripts/setup-web2py-heroku.sh
>>> https://github.com/web2py/web2py/blob/master/gluon/contrib/heroku.py
>>>
>>> I already had a working postgres database from a previous deployment so
>>> I uploaded that from my workstation to the heroku environment using the
>>> heroku postgres restore tool. I had to use fake_migrate_all to get a
>>> working DB without any tickets. Is there a smart way to get DB migrations
>>> working on Heroku itself when you already have a DB?
>>>
>>> To clarify:
>>> Should I rename local .table files with another prefix, matching the
>>> Heroku postgres connection URI and upload them also when I deploy a new
>>> version of the app, or is there a better way?
>>>
>>>
>>>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
