Yes I did.
On Wednesday, May 2, 2018 at 8:55:11 PM UTC+5:30, Mario R. Osorio wrote:
-- 1) I installed all the required packages.
2) Added to Installed apps.
Here is my settings.py file :-
"""
Django settings for crypto project.
Generated by 'django-admin startproject' using Django 2.0.
For more information on this file, see
https://docs.djangoproject.com/en/2.0/topics/settings/
For the full list of settings and their values, see
https://docs.djangoproject.com/en/2.0/ref/settings/
"""
import os
# Build paths inside the project like this: os.path.join(BASE_DIR, ...)
BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
# Quick-start development settings - unsuitable for production
# See https://docs.djangoproject.com/en/2.0/howto/deployment/checklist/
# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY = 'll8(-7j1l%$xmr269^s1%k(wkdki72zd=ngg@$mnr5-ac!%_8-'
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = True
ALLOWED_HOSTS = []
# Application definition
INSTALLED_APPS = [
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'cryptoassets.django',
'cryptoassets.core',
]
MIDDLEWARE = [
'django.middleware.security.SecurityMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
]
ROOT_URLCONF = 'crypto.urls'
TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [],
'APP_DIRS': True,
'OPTIONS': {
'context_processors': [
'django.template.context_processors.debug',
'django.template.context_processors.request',
'django.contrib.auth.context_processors.auth',
'django.contrib.messages.context_processors.messages',
],
},
},
]
WSGI_APPLICATION = 'crypto.wsgi.application'
# Database
# https://docs.djangoproject.com/en/2.0/ref/settings/#databases
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
}
}
# Password validation
# https://docs.djangoproject.com/en/2.0/ref/settings/#auth-password-validators
AUTH_PASSWORD_VALIDATORS = [
{
'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator',
},
]
# Internationalization
# https://docs.djangoproject.com/en/2.0/topics/i18n/
LANGUAGE_CODE = 'en-us'
TIME_ZONE = 'UTC'
USE_I18N = True
USE_L10N = True
USE_TZ = True
# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/2.0/howto/static-files/
STATIC_URL = '/static/'
# TESTNET settings
CRYPTOASSETS = {
# It is recommended to use separate database for cryptoassets,
# but you can share the database with Django as well.
# In any case, cryptoassets
# will use a separate db connection.
# cryptoassets.django does not read the existing DATABASES setting.
# Configure the connection using SQLAlchemy syntax:
# http://cryptoassetscore.readthedocs.org/en/latest/config.html#database
"database": {
"url": "postgresql:///cryptoassets",
"echo": False,
},
# Configure block.io API service with Bitcoin testnet
# (let's not play around with real Bitcoins yet)
"coins": {
"btc": {
"backend": {
"class": "cryptoassets.core.backend.blockio.BlockIo",
"api_key": "887c-1a48-6c1f-ev64",
"network": "btctest",
"pin": "icemanuser",
# Cryptoassets helper process will use this UNIX named pipe to communicate
# with bitcoind
"walletnotify": {
"class": "cryptoassets.core.backend.sochainwalletnotify.SochainWalletNotifyHandler",
"pusher_app_key": "e9f5cc20074501ca7395"
},
}
},
},
# Bind cryptoassets.core event handler to Django dispacth wrapper
"events": {
"django": {
"class": "cryptoassets.core.event.python.InProcessEventHandler",
"callback": "cryptoassets.django.incoming.handle_tx_update"
}
},
# Start simple status at port 9001 for diagnostics
"status_server": {
"ip": "127.0.0.1",
"port": 9001
}
}
On Wednesday, May 2, 2018 at 8:55:11 PM UTC+5:30, Mario R. Osorio wrote:
You need to give more details, such as:
- Did you PIP the application?
- Did you remember to add it to INSTALLED_APPS?
On Wednesday, May 2, 2018 at 7:10:31 AM UTC-4, Hitesh Goyal wrote:Hi,I am trying to configure the cryptoassets.core library for bitcoin applications using the following url : -When i run the command :-"python manage.py cryptoassets_helper_service" I am getting the following error :-ImportError: No module named 'cryptoassets.core.backend.sochainwalletnotify' I want to ask where and how to configure the cryptoassets_helper_service. Please suggest how can i integrate the library.
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+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/f2116e7e-8c2b-4ff9-88fc-c61fc26982e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment