Re: Exciting Opportunity: Join Our Django WhatsApp Bulk Messaging Project!

2024-02-19 Thread Victoria Adebiyi Precious 
I'm interested

On Mon, 19 Feb 2024, 9:33 am Theresa Taye,  wrote:

> I am interested
>
> On Sun, Feb 18, 2024, 5:48 PM SURAJ TIWARI  wrote:
>
>>  Join Our Django WhatsApp Bulk Messaging Project!
>>
>>  Hello everyone,
>>
>> Are you looking for an exciting opportunity to gain hands-on experience
>> in Django development? Do you want to work on a meaningful project that
>> leverages WhatsApp for bulk messaging? We're thrilled to invite you to join
>> our dynamic team!
>>
>>  Benefits:
>>
>>- Get hands-on experience working on a real-world Django project.
>>- Learn how to leverage WhatsApp for bulk messaging, a valuable skill
>>in today's digital landscape.
>>- Opportunities for hybrid work, allowing flexibility in your
>>schedule.
>>- Collaborate with experienced developers and gain valuable
>>mentorship.
>>- Access to cutting-edge tools and technologies.
>>
>>  Opportunities Available:
>>
>>- Django developers
>>- Frontend developers
>>- UI/UX designers
>>- Quality assurance testers
>>
>> 欄 How to Join: Simply reply to this message expressing your interest,
>> and we'll provide you with all the necessary details to get started on our
>> project.
>>
>> Let's work together to create something amazing and gain valuable
>> experience along the way! ✨
>>
>> Best regards,
>>
>> Suraj Tiwari
>>
>>
>> --
>> 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/e8a705fd-10d9-4c1a-b4ba-0a7b896dbfean%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/CAENBRfP0v9_mS%3DqLicTyf5Hu0K7%2BdJyPAyD_qsQzj%2BahrSSGDA%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/CAE24ABToRcCaSi4__yqcDaj5TRtLjSY%2BLLFYp1q%3DDsUHftN3Ag%40mail.gmail.com.

Re: Who wants to join us to program an app for the play store that will consist of a nutritionist on the phone

2024-01-11 Thread Victoria Adebiyi Precious 
Good day. Is this opportunity still available?
I'm interested. I tried but the number isn't on WhatsApp. If yes, kindly
add me to the group. +2347068452733.
Thank you very much!

On Sat, 30 Dec 2023, 4:12 pm Abdulrahman Abbas, 
wrote:

> I'm interested your WhatsApp number it's either is incomplete or incorrect
> add me to the group +234 9020 3877 75
>
> On Sat, Dec 30, 2023, 12:36 T Y  wrote:
>
>> This is the US tailored ?
>>
>> On Fri, Dec 29, 2023 at 9:58 PM Jorge Bueno 
>> wrote:
>>
>>> I have thought about these functionalities:Structure of the Application
>>> for the play store.
>>> The application will be divided into the following main sections:
>>>
>>>
>>> 1.User Registration:This section will allow users to create accounts and
>>> provide personal information, such as their name, age, gender, weight,
>>> height, food preferences and allergies.
>>>
>>>
>>> 2.Medical Data Integration: This section will allow users to upload and
>>> store relevant medical analyses and results, allowing for a more accurate
>>> assessment of nutritional needs.
>>>
>>>
>>> Personalized Health Profile: This section will allow users to create
>>> detailed health profiles that include information on pre-existing medical
>>> conditions, family history of diseases and other factors affecting diet.
>>>
>>>
>>> Health Goals and Objectives: This section will allow users to set
>>> specific health goals, such as weight loss, muscle gain, blood pressure
>>> control, etc.
>>>
>>>
>>> 5.Smart Recommendation Algorithms: This section will implement advanced
>>> algorithms that will process user information and provide accurate and
>>> personalized recommendations.
>>>
>>>
>>> 6.Nutritional Database: This section will contain an extensive food
>>> database with detailed nutritional information, including calories,
>>> protein, fat, carbohydrates, vitamins and minerals.
>>>
>>>
>>> 7.Diet Tracking: This section will allow users to record daily food
>>> intake.
>>>
>>>
>>> 8.Integration with Health Devices: This section will allow users to
>>> connect with health tracking devices to obtain real-time data.
>>>
>>>
>>> 9.Notifications and Reminders: This section will allow users to receive
>>> notifications and reminders about their diet, health goals and other
>>> health-related activities.
>>>
>>>
>>> 10.Personalized Nutrition Tips: This section will provide educational
>>> nutrition information and personalized tips to help users make healthier
>>> dietary choices.
>>>
>>>
>>> 11.History and Tracking: This section will record the user's diet
>>> history and health progress.
>>>
>>>
>>> 12.Interaction with Health Professionals: This section will allow users
>>> to communicate with health professionals, such as nutritionists, for
>>> personalized advice.
>>>
>>>
>>> Privacy and Security: This section will implement robust privacy and
>>> security measures to protect the user's information.
>>>
>>>
>>> 14.Recipe Customization: This section will allow users to create
>>> customized recipes that fit their preferences and dietary restrictions.
>>>
>>>
>>> Continuous Updates: This section will keep the application updated with
>>> new features, bug fixes and a constantly growing food database.We can
>>> create a wassap group: My wassap is 641015323
>>>
>>> --
>>> 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/61ba02c0-19e4-44d9-be59-6e19bdbbef04n%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/CAAwLT1kHLbED%3DN5dgVHqHm4jceH2D8WpkoDpO3fw%3DRMUsfGNJQ%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/CAGGqo0O70AyCsW%3Db76T7xmgqN43H4U8SyX5JkSTzyDsoxXTLfw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you

Re: ec2 using bitnami djangostack: application never loads; browser just hangs

2014-02-04 Thread victoria 
Hi,

I'm sorry you are finding issues with the Bitnami image. I just saw
this, sorry if it is too late. Which version are you using? Can you
check if the django.conf file (apps/django/conf/django.conf) is
overwriting your /static alias? Also did you give permission to the
daemon user to read your project?

Best regards,

Victoria.

On Thu, Jan 23, 2014 at 4:49 AM, Dylan Bumford <dbumf...@gmail.com> wrote:
> Thanks. I've checked apache's error_log, and it doesn't report anything
> unusual. The access_log reports about four hundred GET requests that look
> sort of like this:
>
> 10.73.205.233 - - [22/Jan/2014:18:07:34 -0500] "GET
> /img/ami-lower-container.png HTTP/1.1" 304 -
> 10.73.205.233 - - [22/Jan/2014:18:07:34 -0500] "GET /img/ami-list-item.png
> HTTP/1.1" 304 -
>
>
> The last two lines are:
>
> 201.249.174.162 - - [22/Jan/2014:18:09:19 -0500] "HEAD / HTTP/1.0" 200 -
> 120.192.101.153 - - [22/Jan/2014:19:21:28 -0500] "GET /manager/html
> HTTP/1.1" 404 210
>
>
> I don't know what other logs to check. When I run the app in DEBUG=True, I
> don't see any difference. If I introduce an artificial bug in
> /mysite/mysite/urls.py, it reports the bug through the Django debugging page
> (and also in error_log). But when I remove the bug, it's back to endless
> waiting. How can I tell if the request is making it to modwsgi or it's stuck
> in apache?
>
> Dylan
>
> On Wednesday, January 22, 2014 12:26:13 PM UTC-5, Andréas Kühne wrote:
>>
>> 1. Have you checked all of the access logs and error logs when the app is
>> started? Is your request getting served by modwsgi, or is it stuck in
>> apache?
>> 2. Start the application with DEBUG=True in settings, to see if you get
>> any information from the app.
>>
>> Thats where I'd start.
>>
>> Regards,
>>
>> Andréas Kühne
>>
>>
>> 2014/1/22 Dylan Bumford <dbum...@gmail.com>
>>>
>>> I used the Bitnami Djangostack AMI to set up a Django environment with
>>> apache2 and mod_wsgi on a free instance provided by Amazon's EC2. The django
>>> app is installed at /opt/bitnami/apps/django/django_projects/mysite,
>>> alongside the default Project application that comes with the stack. The app
>>> runs on my local computer on the development server without issue. When I
>>> transferred the app to the server, I ran the collectstatic script to copy
>>> all of the static files to mysite/static, and configured the server to serve
>>> STATIC_ROOT at STATIC_URL (settings and configuration details are reported
>>> below). As best I can make out, I've configured everything in accordance
>>> with the Django documentation and modwsgi documentation.
>>>
>>> When I point my browser to the server's public address, I see the bitnami
>>> startup page, but when I point to the subdirectory mapped to the
>>> application, the browser just hangs. It acts as if it's loading a website,
>>> spins the little wheel to tell you it's loading a website, and says 'Waiting
>>> for xx.xxx.xxx.xxx..." But nothing ever happens. There are no errors
>>> reported in /opt/bitnami/apache2/logs/error_log. But If I point instead to a
>>> random subdirectory that doesn't exist, I get a 404 page. If I point to the
>>> static subdirectory, I get a 403 Forbidden page. If I purposefully add a bug
>>> to any of the python code (in e.g. mysite/mysite/urls.py or
>>> mysite/myapp/views.py), I get a 500 Internal Server Error and a message in
>>> the error_log with the expected python stack trace.
>>>
>>> If anyone has any suggestions, I would obviously be very grateful. I'm
>>> pretty new to this.
>>>
>>> Here are the relevant parts of my configuration files.
>>>
>>>
>>> /opt/bitnami/apache2/conf/httpd.conf
>>>
>>> ServerRoot "/opt/bitnami/apache2"
>>> Listen 80
>>> 
>>> User daemon
>>> Group daemon
>>> 
>>> ServerName localhost:80
>>> DocumentRoot "/opt/bitnami/apache2/htdocs"
>>> 
>>> Options Indexes FollowSymLinks
>>> AllowOverride None
>>> 
>>> LoadModule wsgi_module modules/mod_wsgi.so
>>> WSGIPythonHome /opt/bitnami/python
>>> Include "/opt/bitnami/apps/django/conf/mysite.conf"
>>>
>>>
>>>
>>> /opt/bitnami/apps/django/conf/mysite.conf
>>>
>>> Alias /static "opt/bitnami/apps/django/django_projects/mysite/static"
>>>
>>> 
>>> Order deny,allow
>>>

Re: server error (500)

2013-07-25 Thread victoria 
The error log doesn't show anything. In which step following the
documentation are you getting this error?

On Thu, Jul 25, 2013 at 12:09 PM, Oliver <odav...@gmail.com> wrote:
> my environment is in my local pc or machine so its a development machine.
>
> I tried that empy field in allowed_host.
>
>
>
>
>
> On Thursday, July 25, 2013 5:43:02 AM UTC-4, Mário Idival wrote:
>>
>> use this in your settings.py
>> ALLOWED_HOSTS = []
>>
>> where are you envirioment? you app there in production or development?
>> Em 25/07/2013 04:35, "victoria" <ka...@bitrock.com> escreveu:
>> >
>> > Hi,
>>
>> >
>> > On Thu, Jul 25, 2013 at 4:30 AM, Oliver <oda...@gmail.com> wrote:
>> > > If I set DEBUG = False, I get this
>> > >
>> > > It worked!
>> > >
>> > > Congratulations on your first Django-powered page.
>> > >
>> > > Of course, you haven't actually done any work yet. Here's what to do
>> > > next:
>> > >
>> > > If you plan to use a database, edit the DATABASES setting in
>> > > mysite/settings.py.
>> > > Start your first app by running python manage.py startapp [appname].
>> > >
>> > > You're seeing this message because you have DEBUG = True in your
>> > > Django
>> > > settings file and you haven't configured any URLs. Get to work!
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > If I set it to true, I get the server error (500).  I created the
>> > > template
>> > > and static folder inside mysite folder.  Here is my setting.py.
>> > >
>> >
>> > Can  you check the apache error log to see if you can find more
>> > information there? It is located in
>> > C:\BitNami\djangostack-1.5.1-0\apache2\logs
>> >
>> >
>> > > I run the inspectdb and it went fine, no errors.   I'm new and
>> > > following the
>> > > tutorials at Django website documentation.
>> > >
>> > > I appreciate any help.
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > # Django settings for mysite project.
>> > >
>> > > DEBUG = True
>> > > TEMPLATE_DEBUG = DEBUG
>> > >
>> > > ADMINS = (
>> > > # ('mysite', 'em...@email.com'),
>>
>> > > )
>> > >
>> > > MANAGERS = ADMINS
>> > >
>> > > DATABASES = {
>> > > 'default': {
>> > > 'ENGINE': 'django.db.backends.mysql', # Add
>> > > 'postgresql_psycopg2',
>> > > 'mysql', 'sqlite3' or 'oracle'.
>> > > 'NAME': 'mysitedb',  # Or path to database
>> > > file
>> > > if using sqlite3.
>> > > # The following settings are not used with sqlite3:
>> > > 'USER': 'root',
>> > > 'PASSWORD': '',
>> > > 'HOST': '',  # Empty for localhost through
>> > > domain sockets or '127.0.0.1' for localhost through TCP.
>> > > 'PORT': '',  # Set to empty string for
>> > > default.
>> > > }
>> > > }
>> > >
>> > > # Hosts/domain names that are valid for this site; required if DEBUG
>> > > is
>> > > False
>> > > # See
>> > > https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-hosts
>> > > ALLOWED_HOSTS = ['localhost']
>> > >
>> > > # Local time zone for this installation. Choices can be found here:
>> > > # http://en.wikipedia.org/wiki/List_of_tz_zones_by_name
>> > > # although not all choices may be available on all operating systems.
>> > > # In a Windows environment this must be set to your system time zone.
>> > > TIME_ZONE = 'EST'
>> > >
>> > > # Language code for this installation. All choices can be found here:
>> > > # http://www.i18nguy.com/unicode/language-identifiers.html
>> > > LANGUAGE_CODE = 'en-us'
>> > >
>> > > SITE_ID = 1
>> > >
>> > > # If you set this to False, Django will make some optimizations so as
>> > > not
>> > > # to load the internationalization machinery.
>> > > USE_I18N = True
>> > >
>> > > # If you set this to False, Dja

Re: server error (500)

2013-07-25 Thread victoria 
Hi,

On Thu, Jul 25, 2013 at 4:30 AM, Oliver  wrote:
> If I set DEBUG = False, I get this
>
> It worked!
>
> Congratulations on your first Django-powered page.
>
> Of course, you haven't actually done any work yet. Here's what to do next:
>
> If you plan to use a database, edit the DATABASES setting in
> mysite/settings.py.
> Start your first app by running python manage.py startapp [appname].
>
> You're seeing this message because you have DEBUG = True in your Django
> settings file and you haven't configured any URLs. Get to work!
>
>
>
>
>
> If I set it to true, I get the server error (500).  I created the template
> and static folder inside mysite folder.  Here is my setting.py.
>

Can  you check the apache error log to see if you can find more
information there? It is located in
C:\BitNami\djangostack-1.5.1-0\apache2\logs


> I run the inspectdb and it went fine, no errors.   I'm new and following the
> tutorials at Django website documentation.
>
> I appreciate any help.
>
>
>
>
>
>
>
> # Django settings for mysite project.
>
> DEBUG = True
> TEMPLATE_DEBUG = DEBUG
>
> ADMINS = (
> # ('mysite', 'em...@email.com'),
> )
>
> MANAGERS = ADMINS
>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.mysql', # Add 'postgresql_psycopg2',
> 'mysql', 'sqlite3' or 'oracle'.
> 'NAME': 'mysitedb',  # Or path to database file
> if using sqlite3.
> # The following settings are not used with sqlite3:
> 'USER': 'root',
> 'PASSWORD': '',
> 'HOST': '',  # Empty for localhost through
> domain sockets or '127.0.0.1' for localhost through TCP.
> 'PORT': '',  # Set to empty string for default.
> }
> }
>
> # Hosts/domain names that are valid for this site; required if DEBUG is
> False
> # See https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-hosts
> ALLOWED_HOSTS = ['localhost']
>
> # Local time zone for this installation. Choices can be found here:
> # http://en.wikipedia.org/wiki/List_of_tz_zones_by_name
> # although not all choices may be available on all operating systems.
> # In a Windows environment this must be set to your system time zone.
> TIME_ZONE = 'EST'
>
> # Language code for this installation. All choices can be found here:
> # http://www.i18nguy.com/unicode/language-identifiers.html
> LANGUAGE_CODE = 'en-us'
>
> SITE_ID = 1
>
> # If you set this to False, Django will make some optimizations so as not
> # to load the internationalization machinery.
> USE_I18N = True
>
> # If you set this to False, Django will not format dates, numbers and
> # calendars according to the current locale.
> USE_L10N = True
>
> # If you set this to False, Django will not use timezone-aware datetimes.
> USE_TZ = True
>
> # Absolute filesystem path to the directory that will hold user-uploaded
> files.
> # Example: "/var/www/example.com/media/"
> MEDIA_ROOT = ''
>
> # URL that handles the media served from MEDIA_ROOT. Make sure to use a
> # trailing slash.
> # Examples: "http://example.com/media/;, "http://media.example.com/;
> MEDIA_URL = ''
>
> # Absolute path to the directory static files should be collected to.
> # Don't put anything in this directory yourself; store your static files
> # in apps' "static/" subdirectories and in STATICFILES_DIRS.
> # Example: "/var/www/example.com/static/"
> #STATIC_ROOT = ''
>
> # URL prefix for static files.
> # Example: "http://example.com/static/;, "http://static.example.com/;
> STATIC_URL = '/static/'
>
> # Additional locations of static files
> STATICFILES_DIRS = (
> # Put strings here, like "/home/html/static" or "C:/www/django/static".
> # Always use forward slashes, even on Windows.
> # Don't forget to use absolute paths, not relative paths.
> )
>
> # List of finder classes that know how to find static files in
> # various locations.
> STATICFILES_FINDERS = (
> 'django.contrib.staticfiles.finders.FileSystemFinder',
> 'django.contrib.staticfiles.finders.AppDirectoriesFinder',
> #'django.contrib.staticfiles.finders.DefaultStorageFinder',
> 'C:\BitNami\djangostack-1.5.1-0\mysite\mysite\static',
> )
>
> # Make this unique, and don't share it with anybody.
> SECRET_KEY = '358gds4dg4s0*&^&^lkN0g4ses4rt6strssgs'
>
> # List of callables that know how to import templates from various sources.
> TEMPLATE_LOADERS = (
> 'django.template.loaders.filesystem.Loader',
> 'django.template.loaders.app_directories.Loader',
> # 'django.template.loaders.eggs.Loader',
> )
>
> MIDDLEWARE_CLASSES = (
> 'django.middleware.common.CommonMiddleware',
> 'django.contrib.sessions.middleware.SessionMiddleware',
> 'django.middleware.csrf.CsrfViewMiddleware',
> 'django.contrib.auth.middleware.AuthenticationMiddleware',
> 'django.contrib.messages.middleware.MessageMiddleware',
> # Uncomment the next line for simple clickjacking protection:
> #

Re: Django in the Mac App Store with BitNami

2013-05-21 Thread victoria 
Hi,

On Sat, May 18, 2013 at 7:13 PM, Artem Zinoviev <arzinov...@gmail.com> wrote:
>
> sorry, but why you use apache?

We include Apache and mod_wsgi because it is what most of users use in
production. Of course you can use the django development server.
However when an user tries to configure his application with Apache it
is not always straight forward. Including Apache makes you easier to
test this configuration. Basically we allow you to use the default
server but we also make easier to test your applications with Apache.

one-click deployment in local computer? or
> in heroku?

Local computer. This distribution is mainly intended for development
in your machine. In BitNami we also offer virtual machines and cloud
images with a very similar environment so migrate your apps to
production should be easier. Of course you don't need to use BitNami
for production, you can just use the native installer for development
and then use any other environment for hosting your application.

> Can i use createproject from template?

Yes, you should be able to use it.

>why You don`t like old way
> by - mkvirtualenv spam && pip install django && django-admin.py startproject

Unfortunately applications in the Mac Store are running under a
sandbox which introduce several restrictions one of them is that it is
not compatible with virtualenv. This distribution in the Mac App Store
is mainly intended for getting started with Django (due to the sandbox
restrictions), the users can quickly have a Django environment, open
the official Django documentation and start playing with it. We also
offer native installers for Windows, Linux and Mac OS X (out from the
Mac App Store) which don't have these limitations.

> ?? Django is not CMS... :-)

Of course not. Sorry, do we mention that somewhere in our
documentation? I'd like to fix it.


Thanks for taking the time to take a look at it. I really appreciate
it. Please don't hesitate to let me know any other question or comment
that you may have. Best regards,

Victoria.


>
> четверг, 16 мая 2013 г., 12:46:02 UTC+3 пользователь victoria написал:
>>
>> Hi,
>>
>> I guess that most of you already have a Django development environment set
>> up. However I want to share this with the django users. In BitNami we have
>> been packaging Django for a while together with Python, Apache and
>> MySQL/PostgreSQL and providing one-click deployment options. Now we have
>> prepared a package for the Mac App Store which makes it even easier to get
>> started for Mac OS X users. You need to download BitNami Stack for Django
>> from the Mac App Store and follow the official Django guides. The
>> installation steps can be skipped because BitNami does it for you. I hope
>> you enjoy Django even more with this new deploy option. We wrote a blog post
>> entry about it in case this sounds interesting to you and you want to learn
>> more about this.
>>
>> If you try it please feel free to let me know your comments I would really
>> appreciate to have your feedback.
>>
>> Thanks,
>>
>> Victoria.

-- 
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 post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Django in the Mac App Store with BitNami

2013-05-16 Thread victoria 
Hi,

I guess that most of you already have a Django development environment set
up. However I want to share this with the django users. In BitNami we have
been packaging Django for a while together with Python, Apache and
MySQL/PostgreSQL and providing one-click deployment options. Now we have
prepared a package for the Mac App Store which makes it even easier to get
started for Mac OS X users. You need to download BitNami Stack for Django
from the Mac App
Store<https://itunes.apple.com/us/app/bitnami-stack-for-django/id600558406?l=en>and
follow the official Django guides. The installation steps can be
skipped because BitNami does it for you. I hope you enjoy Django even more
with this new deploy option. We wrote a blog
post<http://blog.bitnami.com/2013/05/django-in-mac-app-store-with-bitnami.html>entry
about it in case this sounds interesting to you and you want to learn
more about this.

If you try it please feel free to let me know your comments I would really
appreciate to have your feedback.

Thanks,

Victoria.

-- 
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 post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: ANNOUNCE: Django 1.5 released

2013-02-27 Thread victoria 
On Tue, Feb 26, 2013 at 8:44 PM, James Bennett  wrote:
> Yup, it's finally here!
>
> * Announcement blog post here:
> https://www.djangoproject.com/weblog/2013/feb/26/15/
> * Release notes here: https://docs.djangoproject.com/en/1.5/releases/1.5/
> * Download it here: https://www.djangoproject.com/download/
>

Django 1.5 version is also already available as a BitNami Stack.
Installers and virtual machines can already be downloaded, cloud
images for Windows Azure and for Amazon cloud will be ready soon.

http://bitnami.org/stack/django

Notice that BitNami DjangoStack already includes PostgreSQL and Posgis
2.0 (for the Linux and Mac versions) so you can easily test the
Geodjango support for Postgis 2.0 without fighting in setting the
right environment :)

> --
> 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 post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
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 post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Problem configuring Django 1.5b2 with PostGIS 2.0

2013-01-28 Thread victoria 
On Fri, Jan 25, 2013 at 5:38 AM, Joe Jasinski <joe.jasin...@gmail.com>wrote:

> I've been experiencing the same issue on OSX 10.8.2.
>
> $ ./manage.py shell
>
> ImproperlyConfigured: Could not import user-defined GEOMETRY_BACKEND
> "geos".
>
> I've installed Postgresapp (http://postgresapp.com/documentation), which
> includes Postgres 9.2.2, PostGIS 2.0.2, GEOS 3.3.5, and Proj (not sure of
> the version, but likely recent).  Note: I also got the same error when
> installing postgres from homebrew.  Various tutorials indicate that I
> should set the following in settings.py.  (
> http://wiki.bitnami.org/Components/Django/GoeDjango_with_PostGIS_Quick_Start_Guide
> )
>
>
> GDAL_LIBRARY_PATH="/Applications/Postgres.app/Contents/MacOS/lib/libgdal.dylib"
>
> GEOS_LIBRARY_PATH="/Applications/Postgres.app/Contents/MacOS/lib/libgeos_c.dylib"
> GDAL_DATA="/Applications/Postgres.app/Contents/MacOS/share/gdal"
>
> Upon doing so, I get a different error.
>
> OSError:
> dlopen(/Applications/Postgres.app/Contents/MacOS/lib/libgeos_c.dylib, 6):
> Library not loaded: @executable_path/../lib/libgeos-3.3.5.dylib
>   Referenced from:
> /Applications/Postgres.app/Contents/MacOS/lib/libgeos_c.dylib
>   Reason: image not found
>
> Below is evidence that the files from PATH statements above do exist.
>
> $ ls -la /Applications/Postgres.app/Contents/MacOS/lib/libgdal.dylib
> lrwxr-xr-x@ 1 jjasinski  staff  15 Jan 24 20:56
> /Applications/Postgres.app/Contents/MacOS/lib/libgdal.dylib ->
> libgdal.1.dylib
>
> $ ls -la /Applications/Postgres.app/Contents/MacOS/lib/libgeos_c.dylib
> lrwxr-xr-x@ 1 jjasinski  staff  17 Jan 24 20:56
> /Applications/Postgres.app/Contents/MacOS/lib/libgeos_c.dylib ->
> libgeos_c.1.dylib
>
> $ ls -ald /Applications/Postgres.app/Contents/MacOS/share/gdal
> drwxr-xr-x@ 47 jjasinski  staff  1598 Jan 24 20:56
> /Applications/Postgres.app/Contents/MacOS/share/gdal
>
> My next step is to try to get this running in an Ubuntu virtual machine,
> but I'd really like to get it work natively in OSX.
>


I see that you include a reference to the BitNami documentation, however
just to confirm, none of you is working with the BitNami Django Stack,
right? In any case the documentation although tested with BitNami should be
quite general. Maybe it is a compatibility issue with the different
components. Also you mentioned that you'd like to get it working on OS X,
have you tried BitNami? It should work, or at least we may be able to
provide support if you find any issue.

Best regards,

Victoria.



>
>
> On Friday, December 28, 2012 11:05:57 AM UTC-6, Odagi wrote:
>>
>> Hi, I have been struggling for two days to get a GeoDjango/PostGIS
>> project started and I'll appreciate any help. Thanks
>>
>> == My project ==
>>
>> Two virtual machines:
>>Machine 1: Running Django 1.5b2
>>Machine 2: Running a geospatial DB server (postgresql-server-dev-9.1,
>> **geos-3.3.5, proj-4.8.0, **postgis-2.0.2)
>>
>> == My (wrong??) assumption ==
>>
>> I don't need to install any geos/postgis library on Machine 1. Please
>> let me know if this is incorrect.
>>
>> == My Problem ==
>>
>> When I run:
>> $  manage.py validate
>>
>> The result is:
>> ImproperlyConfigured: Could not import user-defined GEOMETRY_BACKEND
>> "geos".
>>
>> == Tring to fix this ==
>>
>> In Machine 1 (where I have my Django application), I include this line in
>> settings.py
>>
>> GEOS_LIBRARY_PATH = '/opt/geos/lib/libgeos_c.so'
>>
>> But this path is the location of Geos library in Machine 2 (my DB server).
>> When I run $ manage.py validate, I get this error:
>>
>> OSError: /opt/geos/lib/libgeos_c.so: cannot open shared object file: No
>> such file or directory
>>
>> So, may be I need some Geos libraries in Machine 1 in order to Django
>> communicate with PostGIS, but I'm not sure.
>> Any ideas?
>>
>>
>>
>>
>>
>>
>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [ANNOUNCE] Django 1.5 release candidate available

2013-01-14 Thread victoria 
It took us a while in BitNami...but you can already find the installers,
virtual appliances and cloud images for Django 1.5c1 in
http://bitnami.org/stack/django. Also mention that the Cloud images for
Django 1.4.3 are now also available for Microsoft Azure Cloud. You can
learn more about how to launch these images in http://bitnami.org/azure

Best regards,

Victoria.

On Fri, Jan 4, 2013 at 8:10 PM, Sultan Imanhodjaev <
sultan.imanhodj...@gmail.com> wrote:

> Cool! :) Happy New Year! Trying out RC1
>
>
> On Sat, Jan 5, 2013 at 1:07 AM, James Bennett <ubernost...@gmail.com>wrote:
>
>> 1.5 is almost here!
>>
>> Today marks the release candidate, which you can read about on the weblog:
>>
>> https://www.djangoproject.com/weblog/2013/jan/04/15-rc-1/
>>
>> Assuming no release-blocking bugs, Django 1.5 will be released next week.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To post to this group, send email to django-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> django-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/django-users?hl=en.
>>
>>
>
>
> --
> Kind regards,
> Sultan Imanhodjaev
> +996 559 06 76 06
> PGP 0x4E357296
> http://imanhodjaev.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: [ANNOUNCE] Security releases (Django 1.3.5, Django 1.4.3, Django 1.5 beta 2)

2012-12-14 Thread victoria 
On Mon, Dec 10, 2012 at 11:38 PM, James Bennett <ubernost...@gmail.com> wrote:
> Django 1.3.5, Django 1.4.3 and Django 1.5 beta 2 have just been issued
> in response to security issues.
>
> Details are available here:
>
> https://www.djangoproject.com/weblog/2012/dec/10/security/
>

It has taken a bit for us (BitNami) but we have now updated the three
versions of BitNami Django Stack to include these latest Django
versions with the security fixes. You can get them from
http://bitnami.org/stack/djangostack.

Best regards,

Victoria.

> --
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: [ANNOUNCE] Django 1.5 beta 1 released

2012-11-29 Thread victoria 
On Tue, Nov 27, 2012 at 11:17 PM, James Bennett <ubernost...@gmail.com> wrote:
> Our second milestone on the road to Django 1.5 came today, with the
> release of the first beta package.
>
> Blog post about it is here:
>
> https://www.djangoproject.com/weblog/2012/nov/27/15-beta-1/
>
> Release notes are here:
>
> https://docs.djangoproject.com/en/dev/releases/1.5-beta-1/
>
> And you can get the alpha from the downloads page:
>
> https://www.djangoproject.com/download/
>

We have also updated the BitNami DjangoStack to include 1.5 beta1. The
stack also includes PostgreSQL 9.2.1 with PostGIS 2.0.1 so now that
GeoDjango supports PostGIS 2.0 you can easily test it. Here you can
find a few notes:
http://blog.bitnami.org/2012/11/django-15-beta-geodjango-support-for.html
The native installers, Ubuntu virtual machines and Amazon Cloud images
are available in http://bitnami.org/stack/djangostack

Cheers,

Victoria.



> --
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Unable to deploy due to a WSGI Error

2012-07-06 Thread victoria 
>>
>> Let me quickly introduce the contents of the files to make the case more
>> concrete.
>> This is my /etc/apache2/sites-available/default file

I think that this is the problem. That file is not loaded by the
Apache server included with BitNami. You would need to add a new
include line in /opt/bitnami/apache2/conf/httpd.conf pointing to that
file. To follow the BitNami conventions I would create a file
/opt/bitnami/apps/django/conf/yourproject.conf which would include the
VirtualHost and all the Apache configuration for your project. Then in
/opt/bitnami/apache2/conf/httpd.conf add the following:

Include "/opt/bitnami/apps/django/conf/yourproject.conf"

After that restart the Apache server with /opt/bitnami/ctlscript.sh
restart apache.



>>
>> 
>> ServerAdmin root@***
>> ServerName ***
>>
>> Alias /site_media/
>> /opt/bitnami/apps/django/django_projects/***/site_media/
>> Alias /static/
>> /opt/bitnami/apps/django/lib/python2.7/site-packages/django/contrib/admin/static/
>> Alias /robots.txt
>> /opt/bitnami/apps/django/django_projects/***/site_media/robots.txt
>> Alias /favicon.ico
>> /opt/bitnami/apps/django/django_projects/***/site_media/favicon.ico
>>
>> CustomLog "|/usr/sbin/rotatelogs
>> /opt/bitnami/apps/django/django_projects/logs/access.log.%Y%m%d-%H%M%S 5M"
>> combined
>> ErrorLog "|/usr/sbin/rotatelogs
>> /opt/bitnami/apps/django/django_projects/logs/error.log.%Y%m%d-%H%M%S 5M"
>> LogLevel warn
>>
>> WSGIProcessGroup [***.com]
>> WSGIScriptAlias / /opt/bitnami/apps/django/scripts/django.wsgi
>>
>> 
>> Order deny,allow
>> Allow from all
>> Options -Indexes FollowSymLinks
>> 
>>
>> 
>> Order deny,allow
>> Allow from all
>> 
>> 
>> This is my /opt/bitnami/apps/django/scripts/django.wsgi file
>> import os, sys
>>
>> sys.path.append('/opt/bitnami/apps/django/lib/python2.7/site-packages/')
>> sys.path.append('/opt/bitnami/apps/django/django_projects')
>> sys.path.append('/opt/bitnami/apps/django/django_projects/***')
>> os.environ['DJANGO_SETTINGS_MODULE'] = '***.settings'
>>
>> import django.core.handlers.wsgi
>>
>> application = django.core.handlers.wsgi.WSGIHandler()
>> Here is the relevant portion of /opt/bitnami/apache2/conf/httpd.conf file:
>> ServerRoot "/opt/bitnami/apache2"
>> Listen 80
>> ServerName [***.com]
>> DocumentRoot "/opt/bitnami/apache2/htdocs"
>> LoadModule wsgi_module modules/mod_wsgi.so
>> WSGIPythonHome /opt/bitnami/python
>> Include "/opt/bitnami/apache2/conf/ssi.conf"
>> Include "/opt/bitnami/apps/django/conf/django.conf"
>> Include "/opt/bitnami/apache2/conf/bitnami/httpd.conf"
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/django-users/-/jtSgAF03CiAJ.
>> To post to this group, send email to django-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> django-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/django-users?hl=en.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: GeoDjango on Bitnami DjangoStack problems

2012-06-12 Thread victoria 
On Sat, Jun 9, 2012 at 12:14 AM, jstratm  wrote:
> I posted this over at bitnami too, but perhaps the issue is not with
> the stack and is simply a general user error (highly likely!)
>
> I have been struggling now for about two days to get a GeoDjango/
> PostGIS project started.  Sorry to say, I am fairly new to both Django
> and Linux, but I will do my best to explain what I have tried thus
> far.
>
> First, my assumption: This self contained bitnami djangostack package
> already has everything internally to do a basic Geodjango/PostGIS
> project (I have looked through directories and see them all, but maybe
> they still must be installed?? hmm).  Please let me know if this is
> incorrect.
>
> I am following https://docs.djangoproject.com/en/1.4/ref/contrib/gis/tutorial/
> My steps:
>
> -Installed DjangoStack on Ubunutu 12.4 via the GUI, with all 3 DBs, no
> initial project set up
> -Open up and exclusively work from “use_djangostack” terminal
> -followed the link for “spatial database template” to
> https://docs.djangoproject.com/en/1.4/ref/contrib/gis/install/#spatialdb-template,
> followed directions there:
>        -was NOT able to execute the command “$ sudo su – postgres” (“unknown
> id”) to switch to being a “privileged database user,” BUT I could
> still (mostly) successfully execute:
>        $ POSTGIS_SQL_PATH=/home/jstratman/djangostack-1.4-1/postgresql/share/
> contrib/postgis-        2.0
>        $ createdb -E UTF8 template_postgis
>        $ createlang -d template_postgis plpgsql # Adding PLPGSQL language
> support.
>        (^this command was unsuccessful, stating it already had this language
> support)
>        $ psql -d postgres -c "UPDATE pg_database SET datistemplate='true'
> WHERE   datname='template_postgis';"
>        $ psql -d template_postgis -f $POSTGIS_SQL_PATH/postgis.sql
>        $ psql -d template_postgis -f $POSTGIS_SQL_PATH/spatial_ref_sys.sql
>        $ psql -d template_postgis -c "GRANT ALL ON geometry_columns TO
> PUBLIC;"
>        $ psql -d template_postgis -c "GRANT ALL ON geography_columns TO
> PUBLIC;"
>        $ psql -d template_postgis -c "GRANT ALL ON spatial_ref_sys TO
> PUBLIC;"
> -Moved back to main tutorial page, executed:
>        $ createdb -T template_postgis mysitedatabase
>        $ sudo su – postgres (tried again, NOT SUCCESSFUL! “unknown id”)
>        $ createuser --createdb mysiteuser
>        $ django-admin.py startproject mysite (I stayed in the main
> directory, did not create this in “Apps>Django>Django_Projects”)
>        $ cd mysite
>        $ python manage.py startapp world
> -I then set up the settings.py:
>        DATABASES = {
>    'default': {
>         'ENGINE': 'django.contrib.gis.db.backends.postgis',
>         'NAME': 'mysitedatabase',
>         'USER': 'mysiteuser',
>     }
> }
> INSTALLED_APPS = (
>    'django.contrib.auth',
>    'django.contrib.contenttypes',
>    'django.contrib.sessions',
>    'django.contrib.sites',
>    'django.contrib.messages',
>    'django.contrib.staticfiles',
>    'django.contrib.admin',
>    'django.contrib.gis',
>    'world'
> )
> -I did try adding 'PASSWORD' to the settings.py on my second try but
> that made no difference once I got to the syncdb (see below)
> -Installed world borders shp files in world/data
> -Used both ogrinfo commands and got proper results
> -exactly copied and pasted into world/models.py from the “Defining a
> Geographic Model” section, to include the very top line of “from
> django.contrib.gis.db import models
> “
> The Error:
> -Attempted to run “$ python manage.py sqlall world” but got:
> --
> Traceback (most recent call last):
>  File "manage.py", line 10, in 
>    execute_from_command_line(sys.argv)
>  File "/home/jstratman/djangostack-1.4-1/apps/django/lib/python2.7/
> site-packages/django/core/management/__init__.py", line 443, in
> execute_from_command_line
>    utility.execute()
>  File "/home/jstratman/djangostack-1.4-1/apps/django/lib/python2.7/
> site-packages/django/core/management/__init__.py", line 382, in
> execute
>    self.fetch_command(subcommand).run_from_argv(self.argv)
>  File "/home/jstratman/djangostack-1.4-1/apps/django/lib/python2.7/
> site-packages/django/core/management/__init__.py", line 261, in
> fetch_command
>    klass = load_command_class(app_name, subcommand)
>  File "/home/jstratman/djangostack-1.4-1/apps/django/lib/python2.7/
> site-packages/django/core/management/__init__.py", line 69, in
> load_command_class
>    module = import_module('%s.management.commands.%s' % (app_name,
> name))
>  File "/home/jstratman/djangostack-1.4-1/apps/django/lib/python2.7/
> site-packages/django/utils/importlib.py", line 35, in import_module
>    __import__(name)
>  File "/home/jstratman/djangostack-1.4-1/apps/django/lib/python2.7/
> site-packages/django/core/management/commands/sqlall.py", line 4, in
> 
>    from django.core.management.sql import sql_all
>  File

Re: tutorial part 1...syncing db

2012-04-12 Thread victoria 
On Thu, Apr 12, 2012 at 7:09 PM, Brandy  wrote:
> I am working (again) through the tutorial part 1. I have made changes to
> Engine and Name as specified in the instructions. However, running "python
> manage.py syncdb" continues to return "Please supply the ENGINE value." I
> did not encounter this problem the first time I worked through this
> tutorial.
>
> # Django settings for mysite project.
>
> DEBUG = True
> TEMPLATE_DEBUG = DEBUG
>
> ADMINS = (
>     # ('Your Name', 'your_em...@example.com'),
> )
>
> MANAGERS = ADMINS
>
> DATABASES = {
>     'default': {
>     'ENGINE': 'django.db.backends.sqlite3', # Add 'postgresql_psycopg2',
> 'mysql', 'sqlite3' or 'oracle'.
>     'NAME': 'c:/program files/bitnami
> djangostack/mysite/sqlite3.db',  # Or path to database
> file if using sqlite3.
>     'USER': '',  # Not used with sqlite3.
>     'PASSWORD': '',  # Not used with sqlite3.
>     'HOST': '',  # Set to empty string for
> localhost. Not used with sqlite3.
>     'PORT': '',  # Set to empty string for default.
> Not used with sqlite3.
>     }
> }
>

Your settings seem correct. Which version of django are you using?
Have you checked that the settings.py file is in the correct location
for your django version?

Django 1.4 expects this layout:

mysite/
manage.py
mysite/
__init__.py
settings.py
urls.py
wsgi.py

While Django 1.3 expects this:

mysite/
__init__.py
manage.py
settings.py
urls.py


Since 1.4 was released this seems one of the most common mistakes that
could cause this error.

> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-users/-/qnfmdfEObKAJ.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

BitNami Django Stack with Django 1.4.0

2012-03-28 Thread victoria 
Hi,

I just wanted to let you know that BitNami installers, virtual
machines and AMIs for Django 1.4.0 are already available.

http://bitnami.org/stack/djangostack

I hope you enjoy it and I'd love to hear ther comments and suggestions
that you may have.

Cheers,

Victoria.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: ANN: Django 1.4 release candidate 2 issued

2012-03-15 Thread victoria 
On Thu, Mar 15, 2012 at 4:46 AM, James Bennett <ubernost...@gmail.com> wrote:
> Subject line says it all, and details, as always, are on the weblog:
>
> https://www.djangoproject.com/weblog/2012/mar/14/14rc2/
>

We have also released a new version of BitNami DjangoStack 1.4c2 which
bundles Django 1.4 Release Candidate 2. Native installers and Ubuntu
virtual machines are already available. Amazon Cloud images are in the
way. I'm sure this will make easier to test the new Django version.
Enjoy!

You can get them from http://bitnami.org/stack/djangostack

Cheers,

Victoria.

> --
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django 1.4 beta 1 released

2012-02-16 Thread victoria 
I just wanted to let you know that we have also released a new version
of BitNami DjangoStack 1.4b1 which bundles Django 1.4b1. I hope that
will make easier to test this new version without conflicting with
your current stable environment.

http://bitnami.org/stack/djangostack


On Thu, Feb 16, 2012 at 5:27 AM, James Bennett  wrote:
> Hot off the presses, it's the first Django 1.4 beta! Blog post with
> more information is here:
> https://www.djangoproject.com/weblog/2012/feb/15/14-beta-1/
>
>
> --
> "Bureaucrat Conrad, you are technically correct -- the best kind of correct."
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Cheap Django hosting?

2012-01-05 Thread victoria 
Hi,

I wanted to mention that if you are OK with using EC2 you can also use
the public BitNami DjangoStack AMI (I'm part from the BitNami team).
It includes preconfigured version of Apache with mod_wsgi, django
1.3.1 and Python 2.6.5. It also includes PostgreSQL and MySQL.
Alternatively you can also use BitNami Cloud Hosting that makes easier
the management of your sever (start/stop, basic monitoring, resize
images, schedule backups,...) we offer a free developer plan in which
you will only be charged by the Amazon costs (which you pay directly
to them) so if you are elegible for the free tier, it would be
completely free for the first year.

If you are interested these are the links:
http://bitnami.org/stack/djangostack#cloudImage (the AMI) and
http://bitnami.org/cloud (BCH). I will be glad of answering any
question you may have about the service.

Best regards,

Victoria.

On Thu, Jan 5, 2012 at 6:52 AM, Alec Taylor <alec.tayl...@gmail.com> wrote:
> Interesting, thanks.
>
> On Thu, Jan 5, 2012 at 4:47 PM, Kenneth Reitz <m...@kennethreitz.com> wrote:
>> Heroku gives you 750 free "dyno hours" per month, per app for free.
>>
>> Essentially, they let any app run 24/7 (equivalent to a single server with
>> 512MB of RAM and some pretty beefy processors). Scaling a process to
>> multiple dynos is when the $0.05/hr charge starts (essentially adding
>> another server behind a load balancer).
>>
>>
>>
>> --
>> Kenneth Reitz
>>
>> On Wednesday, January 4, 2012 at 10:20 PM, Alec Taylor wrote:
>>
>> On Thu, Jan 5, 2012 at 4:44 AM, Kenneth Reitz <m...@kennethreitz.com> wrote:
>>
>> You could easily run that on Heroku, and it would cost you $0.
>>
>>
>> I don't understand, why would it cost $0 on Heroku?
>>
>> I checked http://heroku.com/pricing and it seems to cost.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To post to this group, send email to django-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> django-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/django-users?hl=en.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To post to this group, send email to django-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> django-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/django-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: ImportError: No module named django

2011-11-21 Thread victoria 
Hi,

You mentioned that you installed BitNami DjangoStack. For using it you
should first go to the Windows Start Menu and click in the 'Use
DjangoStack" link. Then you can execute python and 'import django'
should work. You also have Python 2.7 installed so if you don't load
the BitNami environment first you will be working with the version of
Python that you installed and that doesn't include django by default.

Best regars,

Victoria.

On Sat, Nov 19, 2011 at 12:52 PM, Tim Makobu
<makobu.mwambir...@gmail.com> wrote:
> Hi,
> Also, If you haven't read ALL of this
> yet http://docs.python.org/tutorial/index.html go ahead and do so.
>
> On Sat, Nov 19, 2011 at 2:29 PM, Jenny <email@gmail.com> wrote:
>>
>> Thank you Furbee. I will try later to to put the unpacked Django in
>> the same folder as setup.py folder. I'll be back soon with the
>> result.
>>
>> On 18 Nov, 23:02, Furbee <furbeena...@gmail.com> wrote:
>> > You can get to the python interactive interpreter by typing "python"
>> > into a
>> > Dos shell, as long as the python executable is in your system path. The
>> > IDLE command line should work, also. In the Python folder there should
>> > be a
>> > site-packages folder which contains a folder named django. The "import
>> > django" command is attempting to import from there by default. So, if
>> > that
>> > is failing, the django site package must not be installed properly. When
>> > you download the Django package as a zip file, extract it to a location.
>> > From that location there is a setup.py file. From a shell go to that
>> > location and enter "python setup.py install". This should install the
>> > Django framework into the Python site-packages folder, and the "import
>> > django" should work from a python shell.
>> >
>> > Cheers,
>> >
>> > Furbee
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Fri, Nov 18, 2011 at 12:14 PM, Jenny <email@gmail.com> wrote:
>> > > I am as newbie as for two hours ago I installed Python 2.7.2 and an
>> > > hour ago installed BitNami DjangoStack 1.3.1 on my Windows 7 machine.
>> > > I am trying to start with a tutorial on the Djangos website which
>> > > says:
>> > > "You can tell Django is installed by running the Python interactive
>> > > interpreter and typing import django"
>> >
>> > > I assume that the "Python interactive interpreter" is IDLE (Python
>> > > GUI). When i run it and on the command line I write "import django", I
>> > > get a message as follwoing:
>> > > >>> import django
>> > > Traceback (most recent call last):
>> > >  File "<pyshell#6>", line 1, in 
>> > >    import django
>> > > ImportError: No module named django
>> >
>> > > Would you please give me help some advice what to do here? Many
>> > > thanks.
>> >
>> > > --
>> > > You received this message because you are subscribed to the Google
>> > > Groups
>> > > "Django users" group.
>> > > To post to this group, send email to django-users@googlegroups.com.
>> > > To unsubscribe from this group, send email to
>> > > django-users+unsubscr...@googlegroups.com.
>> > > For more options, visit this group at
>> > >http://groups.google.com/group/django-users?hl=en.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To post to this group, send email to django-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> django-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/django-users?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.