django-dublin-inn-real-estate

KO | EN

gitlite — search

#javascript #python #hacktoberfest #react #ai #typescript #llm #go #golang #android #machine-learning #rust #deep-learning #linux

django-dublin-inn-real-estate

★ 10 Open GitHub ↗

A web application for a Real Estate Company based in Dublin, Ireland, that allows the user to find a house, being able to filter them by location, property type, or price range.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Dublin Inn Real Estate

The live link can be found <a href="https://dublinnrealestate.herokuapp.com/" target="_blank" rel="noopener">here</a>.

This project was created as part of the Full Stack Software Development course offered by Code Institute.

# Table of Contents

- [Dublin Inn Real Estate](#dublin-inn-real-estate)
- [Table of Contents](#table-of-contents)
- [Briefing](#briefing)
  - [Challenge](#challenge)
  - [Business Rules](#business-rules)
  - [Screens](#screens)
- [User Experience | UX](#user-experience--ux)
  - [Goals](#goals)
    - [Visitor Goals](#visitor-goals)
    - [User Stories](#user-stories)
      - [User](#user)
      - [Admin](#admin)
      - [Developer](#developer)
  - [Design Choices](#design-choices)
    - [Typography](#typography)
    - [Color palette](#color-palette)
- [User Interface | UI](#user-interface--ui)
  - [Skeleton](#skeleton)
- [Features](#features)
  - [Existing Features](#existing-features)
    - [Search Filter](#search-filter)
    - [View all available properties for rent](#view-all-available-properties-for-rent)
    - [See more details about a property.](#see-more-details-about-a-property)
    - [Interested in the property? Schedule a visit!](#interested-in-the-property-schedule-a-visit)
- [Information Architecture](#information-architecture)
  - [Project settings files configuration structure](#project-settings-files-configuration-structure)
    - [Development environment](#development-environment)
    - [Testing environment](#testing-environment)
    - [Production environment](#production-environment)
  - [Data Storage](#data-storage)
    - [Database schema](#database-schema)
    - [User Table](#user-table)
    - [Profile Table](#profile-table)
    - [Property Table](#property-table)
    - [County Table](#county-table)
    - [District Table](#district-table)
    - [Neighborhood Table](#neighborhood-table)
    - [PropertyViewing Table](#propertyviewing-table)
    - [PropertyViewingDate Table](#propertyviewingdate-table)
    - [PropertyViewingTime Table](#propertyviewingtime-table)
- [Technologies Used](#technologies-used)
  - [Languages](#languages)
  - [Frameworks](#frameworks)
  - [Libraries](#libraries)
  - [Tools](#tools)
  - [Other Softwares](#other-softwares)
- [Testing](#testing)
  - [Bugs](#bugs)
  - [* <strong>Resolution</strong>✅: Added ACCOUNT_EMAIL_VERIFICATION = 'none' to settings.py to stop an e-mail verification trying to be sent.](#-resolution-added-account_email_verification--none-to-settingspy-to-stop-an-e-mail-verification-trying-to-be-sent)
  - [Unsolved Issues](#unsolved-issues)
- [Deployment](#deployment)
  - [Forking the GitHub Repository and Running this Project Locally](#forking-the-github-repository-and-running-this-project-locally)
    - [Installing virtualenv](#installing-virtualenv)
    - [Creating a new virtualenv](#creating-a-new-virtualenv)
    - [Activating a virtualenv](#activating-a-virtualenv)
  - [Database setup](#database-setup)
  - [Setting up heroku](#setting-up-heroku)
- [Credits](#credits)
  - [Media](#media)
- [Acknowledgements](#acknowledgements)
- [Disclaimer](#disclaimer)
- [Author](#author)

# Briefing

**Dublin Inn Real Estate** is a specialist rental company across Ireland. Based in Dublin, the company has a simple website that receives around 2,000 simultaneous hits per day.

In just over 1 year of the website, the marketing team of **Dublin Inn Real Estate** noticed that the volume of access to the website was falling, contributing with a significant portion of the company's revenue.

Based on this information, the team of analysts decided to investigate the reason for the decrease in access and found that the site had become obsolete and the system no longer supported the number of daily accesses, which required a redesign of the entire web application. Therefore, the marketing team launched a proposal to innovate the company's visual identity.

## Challenge

Concerned about this metric falling, the CEO of **Dublin Inn Real Estate** hired me to develop a new web application for the company.

At the end of the work, it is expected that a new application will be delivered, with a new identity, new functionalities, reliable and scalable, which supports more simultaneous accesses than the old website.

The company's business team gave me a report on the features that the CEO wants:

> 1. A website whose purpose of the company is immediately understood by the user.
> 2. Have a clear information on what the site is about and what it provides
> 3. Have an easy navigation that is consistent throughout the website
> 4. Consistent layout without any confusing elements
> 5. Accessibility considerations are taken throughout the site
> 6. A form where the user can filter the search by properties, passing information such as location, property type and price range (*This functionality does not exist in the current application*).
> 7. A functionality where the user can schedule a visit to one or more properties and a dashboard where he can view, edit and/or delete a visit (*This functionality does not exist in the current application*).

## Business Rules

The application's administrative functions are intended to manage what each user can do within the system. Permissions such as adding, editing or removing a property, for example, should under no circumstances be given to the user of the application. Such functionalities must be assigned exclusively to the administrator.

In the system, there will be the following user functionalities:

- Admin: has permission in all areas of the system.
   - Users: can edit your own profile like change profile picture or change password. The user can search for properties by **location**, **type** of property (apartment, house, studio, etc.), **price range**, in addition to being able to schedule visits, edit date and time of visit (according to availability) and you can also cancel a certain scheduled visit.

## Screens

- Admin:
    - will be able to manage users.
    - Add/Edit/Remove properties.
    - View all screens users can view as well.
- Users:
    - can log in and out of the application.
    - manage his/her own profile.
    - form to search for properties.

[Back to top ⇧](#table-of-contents)

# User Experience | UX

## Goals

### Visitor Goals

- Provide access to high standard properties for visitors to browse
- Give potential clients a testimonial from previous clients about their satisfaction using the company's services.
- Allow visitors the option to book a property visit directly from the site.
- Allow the visitor to be able to search for a property according to its location, type of property (Studio, Apartment or House) and price.
- Allow the visitor to be able to create an account and manage their own content in the site.

### User Stories

#### User

- As a **Site User** I can **register an account** so that **I can favourite the properties I like and book a visit**.
- As a **Site User** I can **filter a property according to its price** so that **I can choose the one that best suits my budget**.
- As a **Site User** I can **filter a property according to its type** so that **I can choose the one that fits on my needs**.
- As a **Site User** I can **filter a property according to its location** so that **I can choose the one that are of interest to me**.
- As a **Site User** **I can click on a property** so that **I can read the full content**.
- As a **Site User** I can **schedule a day and time** so that **I can visit the property when it's convenient for me**.
- As a **Site User** I can **see all visits scheduled as well as modify or cancel** so that **I can manage my scheduled visits**.
- As a **Site User**, I expect to **have a button** so that I can sign up for the site using my **Facebook** or **Gmail accounts**.

#### Admin

- As a **Site Admin** I want to be able to **add a new property easily**.
- As a **Site Admin** I want to be able to **see all existing properties** in a simple and easy manner.
- As a **Site Admin** I want to be able to **manage the existing properties such as edit price or delete** easily.

#### Developer

- As a **Developer** I want to ensure that **all application features work** as they were implemented to work.
- As a **Developer** I want to ensure **an authenticated user can access** all required information correctly.
- As a **Developer** I want to **work together with the administrator** of the site for **improvements** for the user of the same.

## Design Choices

### Typography

As a primary font, I have chosen to use [Poppins](https://fonts.google.com/specimen/Poppins) as it has a geometric in style, clean, and includes 18 different font weights, from thin to black. Also, Poppins is great for both headlines and paragraph copy to improve readability and style.

As a secondary font I have chosen to use [Fira Sans](https://fonts.google.com/specimen/Fira+Sans) to compliment the site content and allow for the extra content to stand out from the rest of the site content. Furthermore, the Fira font family also aim to cover the legibility needs for a large range of handsets varying in screen quality and rendering.

For the Logo I have chosen to use [Gorditas](https://fonts.google.com/specimen/Gorditas) because it is a fun and funky display slab **serif typeface family**, with heart details, which fit perfectly into the design thought for the project.

### Color palette

Talking to the marketing team at **Dublin Inn Real Estate**, they informed me that the CEO would like the site to have references to the colors of the Irish flag.

With this information I have chosen to use the following colours to provide a great contrast and to help the content stand out.

[Back to top ⇧](#table-of-contents)

# User Interface | UI

## Skeleton

The wireframes were created in [Figma](https://www.figma.com/) which can be explored in details by clicking on the image below 👇

# Features

## Existing Features

### Search Filter

Right on the home page, the user will come across a form where he can search for properties according to location (area), type of property (studio, apartment or house) and price range (min and max).

If the user hits directly on the 'search' button, without adding anything to the search, all properties registered in the system will be returned.

### View all available properties for rent

Still on the home page, the user has the presentation of the properties that are highlighted on the site. However, there is a 'View all' link just above, in the right corner, and when clicking the user will be directed to the properties listing page.

### See more details about a property.

In the list of properties, there is a summary about the property, such as the name of the property, monthly price and some characteristics such as the number of bedrooms, bathrooms, etc.

The user can click on 'See more' to access the specific content of that property. A more detailed page will be presented showing more information about the property, in addition to a map with the location. It is worth mentioning that in this project, the map **is not dynamic**, that is, no API was consumed to return the real location since the property address **does not represent an existing address**.

So, the user should see a page like that.

### Interested in the property? Schedule a visit!

As part of the request made by the CEO of **Dublin Inn Real Estate**, the site will have the option for the user to schedule a visit of a specific property. With that in mind, a 'Schedule your visit' button was developed, which is just below the property description.

Once this is done, the user will be directed to the scheduling form page, which will be as shown in the image below.

Finally, all the schedules that that user has will be displayed. The user can still cancel the appointment if he is unable to attend the scheduled date and time.

[Back to top ⇧](#table-of-contents)

# Information Architecture

## Project settings files configuration structure

The configuration file is one of the most important elements in any Django project. Knowing this, I decided to divide the configuration files structure into four files, one of them being the base file, which will contain everything that is needed in any project environment, be it **production**, **development** or **testing**. The other three files are for development, testing and finally production environments.

For that, create a folder called `settings` inside the main project folder. Inside it, add the `development.py`, `testing.py`, `production.py` and `__init__.py` files. After that, take the base `settings.py` file (which is in the root of the main project folder) and move it into the settings folder.

We will do this so that within the `settings.py` file there are only elements that will be used in any of the environments, be it production, testing or development. However, whatever we need to create differently for each environment, we will put it in the files we just created.

For this project, both the development and test environments use the `sqlite` database locally, while the production environment uses the `Postgresql` database. That way, development and testing data doesn't mix with the data that will be in production. To do this kind of separation, we must place the database settings in their respective files.

See below how the project structure should look 👇

Now, we will need to open each file and add some settings.

### Development environment

```
from .settings import *

DEBUG = True

SECRET_KEY = os.environ.get("SECRET_KEY_DEVELOPMENT")
ALLOWED_HOSTS = ["localhost", "127.0.0.1"]

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.sqlite3',
        'NAME': BASE_DIR / 'db.sqlite3',
    }
}

```

### Testing environment

```
from .settings import *

DEBUG = True
SECRET_KEY = os.environ.get("SECRET_KEY_TESTING")
ALLOWED_HOSTS = ['localhost', '127.0.0.1']

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.sqlite3',
        'NAME': BASE_DIR / 'db.sqlite3',
    }
}
```

### Production environment

```
import os
import dj_database_url
from .settings import *

if os.path.exists("env.py"):
    import env

DEBUG = False
SECRET_KEY = os.environ.get("SECRET_KEY_PRODUCTION")
ALLOWED_HOSTS = [os.environ.get("HEROKU_HOST")]

DATABASES = {'default': dj_database_url.parse(os.environ.get("HEROKU_DB"))}

```

Remembering that it is good programming practices not to leave SECRET_KEYS visible as this will result in the vulnerability of the application. Therefore, generate your own secret keys and configure them through environment variables.

You can use Python `os` library to set your environment variables and then import them into the files, as I exemplify below:

```
import os

# SECRET KEYS
os.environ.setdefault("SECRET_KEY_DEVELOPMENT", "YOUR SECRET KEY")
os.environ.setdefault("SECRET_KEY_PRODUCTION", "YOUR SECRET KEY")
os.environ.setdefault("SECRET_KEY_TESTING", "YOUR SECRET KEY")

```
Once that's done, don't forget to remove the database settings and secret key from the `settings.py` file.

It is worth mentioning that with this change in the project structure, you will need to change some more settings, so that the application works correctly. By default, in the `settings.py` file, the `BASE_DIR` variable looks like this: `BASE_DIR = Path(__file__).resolve().parent.parent`. You will need to add a new `.parent` as there has been a subdivision of the main project folder. So the `BASE_DIR` variable should look like this: `BASE_DIR = Path(__file__).resolve().parent.parent.parent`.

Also, in the `wsgi.py` file you will need to notice that by default, the environment variable setting will look like this:

```
import os

from django.core.wsgi import get_wsgi_application

os.environ.setdefault("DJANGO_SETTINGS_MODULE",
                      "dublinrealestate.settings")

application = get_wsgi_application()
```

Since three independent environments were created, we need to tell Django which environment we are going to work with. In this way, it is necessary to add, right after `settings`, the environment name.

If working in the development environment, add `.development`. If working in the testing environment, add `.testing` and so on.

The same thing should apply to the `manage.py` file which by default appears as

```
import os
import sys

def main():
    """Run administrative tasks."""
    os.environ.setdefault('DJANGO_SETTINGS_MODULE',
                          'dublinrealestate.settings')

# The rest of the code was hidden to optimize the page. Do not remove anything after this line.
    ...
```

If working in the development environment, add `.development` after `settings`. If working in the testing environment, add `.testing` and so on.

Be sure to change it each time you are working in a different environment.

With the project configured correctly, when running the application, you will see something similar to this.

[Back to top ⇧](#table-of-contents)

## Data Storage

### Database schema

### User Table

| Title          | Key In Database | Form Validation           | Data Type   |
| -------------- | --------------- | ------------------------- | ----------- |
| id             | id              | No Validation             | Primary Key |
| Username       | username        | max_length 20             | CharField   |
| First Name     | first_name      | max_lenght 20             | CharField   |
| Last Name      | last_name       | max_lenght 20             | CharField   |
| E-mail Address | email           | Must contain @ & .com etc | Email       |
| Password       | password        | max length 50             | CharField   |

### Profile Table

Once a user registers in the system, a profile is automatically created for that user.

| Title            | Key In Database  | Form Validation                     | Data Type       |
| ---------------- | ---------------- | ----------------------------------- | --------------- |
| Id               | id               | No Validation                       | Primary Key     |
| user             | user             | max length 50                       | Foreign Key     |
| Role             | role             | choices=ROLE_CHOICE*, default=2     | IntegerField    |
| Date of Birthday | date_of_birthday | default=None, null=True, blank=True | DateTimeField   |
| Created at       | created_at       | auto_now_add=True                   | DateTimeField   |
| Updated at       | updated_at       | auto_now_add=True                   | DateTimeField   |
| Token            | token            | max_length=255                      | CharField       |
| Avatar           | avatar           | default='placeholder'               | ImageField      |
| Favourites       | favourites       | blank=True                          | ManyToManyField |

* ROLE_CHOICE = (
    (1, 'Admin'),
    (2, 'Client'),
    (3, 'Agent')
)

### Property Table

* PROPERTY_CATEGORY = (
    (1, 'Sale'),
    (2, 'Rent')
)

* PROPERTY_TYPE = (
    (1, 'Studio'),
    (2, 'Apartment'),
    (3, 'House')
)

### County Table

| Title      | Key in Database | Form Validation   | Data Type     |
| ---------- | --------------- | ----------------- | ------------- |
| Id         | id              | No Validation     | Primary Key   |
| Name       | name            | max length 50     | CharField     |
| Created at | created_at      | auto_now_add=True | DateTimeField |
| Updated at | updated_at      | auto_now_add=True | DateTimeField |

### District Table

| Title      | Key in Database | Form Validation           | Data Type     |
| ---------- | --------------- | ------------------------- | ------------- |
| Id         | id              | No Validation             | Primary Key   |
| Name       | name            | max length 50             | CharField     |
| County     | county          | on_delete=models.SET_NULL | Foreign Key   |
| Created at | created_at      | auto_now_add=True         | DateTimeField |
| Updated at | updated_at      | auto_now_add=True         | DateTimeField |

### Neighborhood Table

| Title      | Key in Database | Form Validation           | Data Type     |
| ---------- | --------------- | ------------------------- | ------------- |
| Id         | id              | No Validation             | Primary Key   |
| Name       | name            | max length 50             | CharField     |
| District   | district        | on_delete=models.SET_NULL | Foreign Key   |
| Created at | created_at      | auto_now_add=True         | DateTimeField |
| Updated at | updated_at      | auto_now_add=True         | DateTimeField |

### PropertyViewing Table

| Title            | Key In Database  | Form Validation                    | Data Type     |
| ---------------- | ---------------- | ---------------------------------- | ------------- |
| Id               | id               | No Validation                      | Primary Key   |
| Property         | property         | on_delete=models.SET_NULL          | Foreign Key   |
| User             | user             | on_delete=models.SET_NULL          | Foreign Key   |
| Day for viewing  | day_for_viewing  | null=False, max_length=20          | CharField     |
| Time for viewing | time_for_viewing | No Validation                      | TimeField     |
| Status           | status           | choices=VIEWING_STATUS*, default=1 | IntegerField  |
| Created at       | created_at       | auto_now_add=True                  | DateTimeField |
| Updated at       | updated_at       | auto_now_add=True                  | DateTimeField |

* VIEWING_STATUS = (
    (1, 'Scheduled'),
    (2, 'Cancelled')
)

### PropertyViewingDate Table

| Title           | Key in Database | Form Validation           | Data Type     |
| --------------- | --------------- | ------------------------- | ------------- |
| Id              | id              | No Validation             | Primary Key   |
| Day for viewing | day_for_viewing | null=False, max_length=20 | CharField     |
| Created at      | created_at      | auto_now_add=True         | DateTimeField |
| Updated at      | updated_at      | auto_now_add=True         | DateTimeField |

### PropertyViewingTime Table

| Title            | Key in Database  | Form Validation   | Data Type     |
| ---------------- | ---------------- | ----------------- | ------------- |
| Id               | id               | No Validation     | Primary Key   |
| Time for viewing | time_for_viewing | No Validation     | TimeField     |
| Created at       | created_at       | auto_now_add=True | DateTimeField |
| Updated at       | updated_at       | auto_now_add=True | DateTimeField |

[Back to top ⇧](#table-of-contents)

# Technologies Used

## Languages

1. **HTML5, or Hyper Text Markup Language:** Used to construct the page within this app -   
https://developer.mozilla.org/en-US/docs/Web/HTML

2. **CSS3, or Cascading Style Sheets:** Used to style the various elements on the app's pages via coloring, fonts, spacing, etc. - 
https://www.w3.org/Style/CSS/Overview.en.html

3. **Javascript:** Used to create iterations across the page. - https://www.javascript.com/

4. **Python:** Used to develop all application logic. (https://www.python.org/)

## Frameworks

- [Django](https://www.djangoproject.com/)
- [Jquery](https://jquery.com/)

## Libraries

- [Django Allauth](https://django-allauth.readthedocs.io/en/latest/installation.html)
- [Daft Listings](https://github.com/AnthonyBloomer/daftlistings)

## Tools

- [Heroku](https://www.heroku.com)
- [Git](https://git-scm.com/)
- [Postgres](https://www.postgresql.org/)
- [Db Diagram](https://dbdiagram.io/home)
- [Figma](https://figma.com)

## Other Softwares

1. **[Am I Responsive?](http://ami.responsivedesign.is/)** : was used in order to see responsive design throughout the process and to generate mockup imagery to be used.

2. **[Responsive Design Tester](https://www.responsivedesignchecker.com/)** : was used to see the responsivity throughout an array of devices (screen sizes) and resolutions.

3. **[Squoosh](https://squoosh.app/)** : was used to reduce the size of the images throughout the page.

[Back to top ⇧](#table-of-contents)

# Testing

Some manual tests were performed to ensure the correct functioning of the application.

- <strong>Implementation</strong> 🔨:
When I had set up the data.json and loaded into the database I could then view all available properties. That way, I could ensure all ones were loaded as expected and that properties information was visible when selected.

- <strong>Test</strong> 🔎:
To test this, I went through each property and loaded the its information page, then looked at changing the url to ensure each item was loading correctly

- <strong>Result</strong> 🏆:
All properties loaded as expected to the main store page. When amending the url all properties again loaded as expected. However, if I tried to access an property slug that didn't exist I was presented with a 404 page.

- <strong>Verdict</strong> ✅:
This test passed and no amendments were required.

---

- <strong>Implementation</strong> 🔨:
As the user can only schedule for visiting a property, I wanted to ensure that the user must be logged in to complete the appointment.

- <strong>Test</strong> 🔎:
To test this I tried to schedule a visit to the property without being logged in. By clicking the 'schedule your visit' button, I was moved directly to the login page. Also, I tried to access the scheduling page directly from the URL and in the same way I was redirected to the login page.

- <strong>Result</strong> 🏆:
The login page was displayed right after I tried to schedule a visit without being properly logged in.

- <strong>Verdict</strong> ✅:
This test completed as expected without bugs.

---

- <strong>Implementation</strong> 🔨:
To test the responsiveness of the site, the page was loaded on local mobile devices to check design choices.

- <strong>Test</strong> 🔎:
This test was performed by loading the site and navigating through each page. In addition, the part where the user can schedule a visit to a property was tested.

- <strong>Result</strong> 🏆:
Each page loaded and displayed correctly with the exception of an issue found in the responsive menu button. When clicking on the button, the user will see the menu opening on the side of the screen. However, when scrolling down the page, the button to close the menu will be at the top of the screen, thus forcing the user to scroll up and then close the menu.

- <strong>Verdict</strong> ❌:
This test was classed as a fail.

---

- <strong>Implementation</strong> 🔨:
To make sure that the user can navigate the site easily, I have tested the navigation of all items, links, buttons, etc., in order to ensure that the user does not get lost within the application sessions.

- <strong>Test</strong> 🔎:
This test was performed in a systematic way, so that each page was navigated, clicked on all the links, in order to ensure that the user knew how to "find himself" within the site.

- <strong>Result</strong> 🏆:
Every page and link was checked and each provided a positive result, in no time was the user sent to an unexpected destination.

- <strong>Verdict</strong> ✅:
This test completed as expected without bugs.

---

## Bugs

* <strong>Problem</strong> 🐞: Account system failed to register user.
* <strong>Cause</strong>🛠: As the sign up was intended to work without having to verify an e-mail address, when sign-up the process failed due to no e-mail setting being available.
* <strong>Resolution</strong>✅: Added ACCOUNT_EMAIL_VERIFICATION = 'none' to settings.py to stop an e-mail verification trying to be sent.
---

## Unsolved Issues

The only known thing, but that is still present on the site, is that when the user searches for a property, passing **only** the **location** parameter, after the 'Dublin 7' area, the result presented does not correspond with the chosen localization. For example, if the user selects the search for Dublin 18, properties from other regions will appear. A different solution would need to be found on the backend to ensure this doesn't happen. I couldn't find a solution before the submission date of this project.

# Deployment

## Forking the GitHub Repository and Running this Project Locally

By forking the GitHub Repository we make a copy of the original repository on our GitHub account to view and/or make changes without affecting the original 
repository by using the following steps...

1. Log in to GitHub and locate the [GitHub Repository](https://github.com/)

2. In the Repository header (not at the top of the page), find a "Code" drop-down button. By clicking this button, you will find some options to clone the project repository. If you have your SSH key configured, choose to select the 'SSH' option and then click on the button right after the url. This button will copy the url and you will paste it in your terminal. If you have not configured your SSH key, you can choose to use the HTTPS protocol. In the same way as was done in the SSH option, when selecting 'HTTPS' you must click on the button right after the url to copy and then paste it into your terminal.

https://github.com/emidiovaleretto/django-dublin-inn-real-estate.git

1. You should now have a copy of the original repository in your GitHub account.

2. Ideally you will want to work within a virtual environment to allow all packages to be kept within the project, this can be installed using the following command (please note some IDE's require pip3 instead of pip, please check with the documentation for your chosen IDE). To create a virtual environment, run the command

### Installing virtualenv

The installation of a virtualenv is done using pip, Python's package manager. It is with it that we install, remove and update packages in our projects. One note is that PIP is already installed when we are using IDE's like VSCode or PyCharm for our Python projects. So, just run the command below to install the virtualenv package on our computer:

pip install virtualenv

Once this is done, the package will be installed and ready to be used. Now you can create and manage your virtual environments.

### Creating a new virtualenv

The process of creating a virtualenv is quite simple and can be done using a single command, as seen below:

virtualenv your_virtualenv_name

*Hint: I usually choose to name my virtual environments after the project name, rather than just writing 'venv', for example, the project is called `MyBlogProject`, so the name of the virtual environment would be something like `myblogenv`. If you need to return to a certain project after a while, you'll easily find the respective environment for that project. But that is totally up to you.*

### Activating a virtualenv

After creating a virtualenv, it's needed to activate it so that you can install the necessary packages for the project. To do this, run the following command:

`source your_virtualenv_name/bin/activate (Linux ou macOS)`

`your_virtualenv_name/Scripts/Activate (Windows)`

3. Once that's done, you need to install the project's dependencies. To do this, just run the following command:

pip3 install -r requirements.txt

4. Next you need to create a new file within the root directory called `env.py`. This file will contain all your secret keys, public keys, production database settings etc. Everything you think should not be exposed, you should put within this file.

So add the following lines to configure the environmental variables.

```
  import os

# SECRET KEYS
  os.environ.setdefault("SECRET_KEY_DEVELOPMENT", "YOUR SECRET KEY")
  os.environ.setdefault("SECRET_KEY_PRODUCTION", "YOUR SECRET KEY")
  os.environ.setdefault("SECRET_KEY_TESTING", "YOUR SECRET KEY")

# DATABASE URL
  os.environ.setdefault("DATABASE_URL", "YOUR DATABASE URL")

```

## Database setup

1. To set up your database you will first need to run the following command:

python3 manage.py migrate

2. Then you need to create a **superuser**. This will allow you to access the application's admin panel. To do so, run the following command in your terminal and fill in the required information as prompted.

python3 manage.py createsuperuser

3. From there you need to delete any objects from the database that are not in the fixture. To do this, run the following commands:

python3 manage.py shell

A terminal screen should appear. In the terminal, paste the following command:

from django.contrib.contenttypes.models import ContentType

ContentType.objects.all().delete()

4. Now you should be able to run the server using the following command:

python3 manage.py runserver

If everything has been correctly configure you should not get a message giving you a link to your locally hosted site usually at http://127.0.0.1:8000

1. Finally, stop the server by pressing CTRL + C (or cmd + C on Mac) and run the following command to populate the database.

python3 manage.py loaddata data.json

After running this command, all information contained in the `data.json` file will be saved in the database. Once that's done, run the `python3 manage.py runserver` command again and you should be able to see the application working.

## Setting up heroku

To set up heroku you must:

1. If your requirements.txt file has not changed you can skip this step. Otherwise, in your terminal type 'pip freeze > requirements.txt' then save and push the changes.
  2. Go to Heroku.com and sign in to your account or create a free one.
  3. From the heroku dashboard click the 'Create new app' button.
  4. Name the app something unique and choose what region you are in then click 'Create app'.
  5. In the resources section, in the *add-ons* field, type `Heroku Postgreslq` and select the free cost option.
  6. Now, go to the settings tab and find the Config Vars section. Click 'Reveal Config Vars'.
   
  In the settings tab, select Reveal Config Vars and copy the pre populated `DATABASE_URL` into your `settings.py` file in your project in the Config Vars in Heroku you will need to populate with the following keys:

7.  Then head over to the deploy section by clicking deploy from the nav bar at the top of the page.
  8.  From the 'Deployment method' section select GitHub and click 'Connect to GitHub'.
  9.  Enter the repository name as it is in GitHub and click 'search'.
  10. Click the 'connect' button next to the repository to link it to heroku.
  11. To deploy, scroll down and click the 'Deploy Branch' button.
  12. Heroku will notify you that the app was successfully deployed with a button to view the app.
  13. If you want to rebuild your app automatically you can also select the 'Enable Automatic Deploys' button which will then rebuild the app every time you push any changes.

# Credits

## Media

- [Pexels](https://www.pexels.com/) - All images were downloaded from the website.
   - [Table of contents](https://ecotrust-canada.github.io/markdown-toc/)
   - [Code Institute](https://codeinstitute.net/)

# Acknowledgements

I would like to take the opportunity to thank:

- To God first, to my family, friends and colleagues for their advice, support and help with testing.
 - To my mentors Felipe Alarcon & Richard Wells for their feedback, advices, support and, above all, for their patience.
 - All Code Institute Tutors and Community on Slack for the peer reviews and advice.

# Disclaimer

> ****Disclaimer***: The following Context is completely fictional, the company, the context, the CEO, the business questions exist only in my imagination.

> **For educational purposes only.

# Author

Made with ❤️ by <b>Emidio Valereto</b> <img src="https://raw.githubusercontent.com/MartinHeinz/MartinHeinz/master/wave.gif" width="16px"> Get in touch!

[![Linkedin Badge](https://img.shields.io/badge/-Emidio-blue?style=flat-square&logo=Linkedin&logoColor=white&link=https://www.linkedin.com/in/emidiovalereto/)](https://www.linkedin.com/in/emidiovalereto/) [![Gmail Badge](https://img.shields.io/badge/-emidio.valereto@gmail.com-c14438?style=flat-square&logo=Gmail&logoColor=white&link=mailto:emidio.valereto@gmail.com)](mailto:emidio.valereto@gmail.com)

[Back to top ⇧](#table-of-contents)

django-dublin-inn-real-estate

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README