How to create a Sitecore Analytics Reporting DB - sitecore

We've got a Sitecore 7.5 installation where we did not deploy any xDB features. There's no Mongo DB or Analytics reporting DBs. We're now exploring upgrading to 8 and turning on these features. I'm doing a test upgrade on a dev server. I've got the Mongo DB set up, but there currently is no Analytics DB in SQL. How do I go about creating that DB?

When you download Sitecore 8 from https://dev.sitecore.net/ there is a zip of the webroot (e.g. from this page). Once you download that webroot zip, you can find the Sitecore.Analytics.mdf and Sitecore.Analytics.ldf files within the \Databases\ folder.

Related

View data on PostgreSQL database in Ubuntu

I am running a Django based website on a Digital Ocean Ubuntu droplet, using PostgreSQL. The site is running and data is being stored in the database successfully.
How do I view the data in the database? I was able to do this easily using PGadmin on my windows machine before I pushed it to production. How do I do this now that there is no GUI?
Can I still use PGadmin somehow and "remote" into my droplet?
Thanks!

Django Web application publishing

How to publish django web application? what are the steps to be followed for publishing a django application? is there any free hosting for pulishing?
thanks in advance
I am using PythonAnyWhere for hosting my project. They provide hosting for python-Django / flask specificly and have a very dedicated team.
You can host your app for free but you can not use your own domain. To use custom domain, you need to purchase paid plan starting from $5 per month.
Their customer support is extremly good.
Steps to follow for hosting:
- Make sure your code is production ready i.e. well tested and bug free.
- Separate production and dev settings file. On production you need to set DEBUG=false.
- Push your code to github. Do not commit sensitive information like credentials or api keys. Keep them in .env file.
- Create account on pythonanywhere server and create database.
- Clone the git repo. Complete the web setup step. Edit the wsgio settings file.
- Run migrations. python manage.py migrate.
- Create cache table if any python manage.py createcachetable.
- Collect static files python manage.py collectstatic.
- Reload the web app.
Refer this step by step article to setup a free account and host web app on pythonanywhere server.
I'm a big fan of Amazon Web Services if you want simplicity and automation. You can create a CodeStar project for Django and Elastic Beanstalk. Everything is set up from you, so as soon as you commit code to your github repo (it even can create the repo for you with the elastic beanstalk config files), it builds, tests, then deploys it.
The best part is you can utilize amazon's free-tier level if you are a new member so it's probably going to be free or extremely cheap.
Look here for reference:
https://aws.amazon.com/codestar/faqs/
digitalocean.com is good for hosting. link
I used this for Django 2.0 with python3.

How to install multiple sitecore 9.0 instance in different CM servers with single database?

I am installing Sitecore 9.0 instance in 2 CM servers. I have successfully installed Sitecore 9.0 instance in first CM server with the database on a different server.
But when I try to install a new Sitecore 9.0 instance in the second CM server it is trying to create a new database. But I want both my Sitecore instance to use the same database created during the first Sitecore 9.0 instance creation.
Please find below the PowerShell commands used to install Sitecore 9.0
Invoke-SitecoreInstall –Path ‘D:\Sitecore\Sitecore 9.0.1 rev. 171219 (WDP XM1 packages)\XM1 Configuration files 9.0.1 rev. 171219\sitecore-solr.json’
Invoke-SitecoreInstall –Path ‘D:\Sitecore\Sitecore 9.0.1 rev. 171219 (WDP XM1 packages)\XM1 Configuration files 9.0.1 rev. 171219\sitecore-XM1-cm.json’
You can't easily skip the database creation step in sitecore-XP1-cm.json, but as a quick solution you can simply change the SqlDbPrefix parameter when running the installation script on the second CM instance. As a result it will still create another set of databases what you can delete later. And on the successful completion of the Sitecore installation script you will need to change the connection strings on the second CM in ../App_Config/ConnectionStrings.config to point it the databases you want to use.

How to deploy django project and postgreSQL from localhost to Digital ocean

I have developed django project on my computer. I used virtuelenv and installed all libraries and packages there. I also have postgreSQL database on my computer. How could I deploy my existing server with all files and libraries, my postgreSQL database with all tables and all rows to digitalocean. I only found tutorials on how to create new django projects on digitalocean.
Actually there is plenty of tutorials and documentation for doing this.
https://www.digitalocean.com/community/tags/django?type=tutorials
In the other hand you only have to migrate your data base from your computer to your new server. Maybe you should check this

Creating a development environment for Django

We are starting a web project with Django (and are pretty new to this), and I was wondering what would been the best way to setup a productive development environment.
Here is some info:
We are 2 developers working on the project
We have a development/production server hosted on Webfactional (using an apache server)
The DB (MySQL) is hosted on this server
We are both using Eclipse with Pydev
The project is hosted on a Github repository
So far, we didn't setup any local development server, we are syncing modifications to the server through Github. But it is not really convenient...
We were thinking of setting up apache servers locally, that uses the remote database, and only sync once in a while.
Do you think it would be better?
Do you have other ideas/additional tips?
Thanks!
Don't try and share servers and databases while you're developing. You'll only get confused.
Each developer should have a local copy of MySQL on their own machine, and run the development server as mipadi recommends. Manage db schema changes via South, and keep data in fixtures or use South's data migrations. Each developer should commit to their local version of the git repository, but only push changes to Github when the particular task is complete and working (or, better, use a remote branch so that changes are synched, but only merge back to master when complete).
A good idea is to have a continuous integration server like Hudson/Jenkins that, after each commit to master, runs the tests and - if they pass - builds an up-to-date version of the site, which you can use for functional/user testing.
Edit to add There's no relationship between the development server and any particular database backend. As I recommend above, it is quite simple to install MySQL or PostgreSQL on your local machine, and use the development server against that. I have been working this way for several years, after initially encountering some of the issues you were worried about when switching between sqlite3 and the production MySQL db.
Django has its own development server that you can use for local testing.