- #AWS POSTGRESQL APACHE DJANGO SOFTWARE LICENSE#
- #AWS POSTGRESQL APACHE DJANGO INSTALL#
- #AWS POSTGRESQL APACHE DJANGO CODE#
- #AWS POSTGRESQL APACHE DJANGO PASSWORD#
Now that the local and host repositories mirror each other, we’ll build the site using a similar docker-compose command.
#AWS POSTGRESQL APACHE DJANGO INSTALL#
The docker-compose commands will fetch version 1.21.2 if there is a more recent version available, change that portion of the command.ĭocker: $ sudo apt update $ sudo apt install apt-transport-https ca-certificates curl software-properties-common $ curl -fsSL | sudo apt-key add - $ sudo add-apt-repository "deb bionic stable" $ sudo apt update $ apt-cache policy docker-ce # shows versions $ sudo apt install docker-ce $ sudo systemctl status docker # checks statusĭocker-compose: $ sudo curl -L `uname -s`-`uname -m` -o /usr/local/bin/docker-compose $ sudo chmod +x /usr/local/bin/docker-compose $ docker-compose -version # check version I won’t be explaining them or listing their outputs. Listed below are all the terminal commands that we’ll need to get Docker and Docker-compose up and running. I find I typically just want the terminal commands in a list, in a centralized place, where I don’t have to go looking for them. I also go through the Step 2 - Running a Container with Docker Compose portion of the docker-compose tutorial. Note: I don’t go through the optional Executing the Docker Command Without Sudo section of the Docker tutorial.
I didn’t run into any issues doing this, and it’s fairly quick. We’ll now need to set up Docker and docker-compose using the following two DigitalOcean tutorials. The new user will now be a mod, and you’ll be acting as the new user. The shell commands are below, and an in-depth tutorial is available on DigitalOcean here. Replace the IP above with your droplet’s IP.Ĭreate a user and give it administrative permissions. I’ll use the flare -i for every SSH, as they’ll be different per project. I utilize SSH keys specific to each project. $ ssh -i cookiecutter_example # replace the IP We’ll begin creating our environment for the application to run. SSH into the server using your root account.
#AWS POSTGRESQL APACHE DJANGO PASSWORD#
done PostgreSQL is available Username: matthewadmin # This is only local Email address: Password: Password (again): Superuser created successfully.Īt this point, we’d be able to make our local changes and add applications, packages, etc. $ docker-compose -f local.yml run -rm django python manage.py createsuperuser Starting postgres. Next, we create a superuser for the database. This will create postgres and django containers. Ensure you don’t have any other Docker containers with the same names running simultaneously. You’ll get a massive amount of output from the terminal as it downloads extensions and builds the virtual environments locally.
#AWS POSTGRESQL APACHE DJANGO CODE#
$ code cookiecutter_example # I use VS Code $ cd cookiecutter_example $ docker-compose -f local.yml up -build -d # build the project in # detached mode
I won’t be explaining much from the Docker perspective. Because we’re using Docker it’ll look a little different than if we were using pure Django however, that’s easily referenced in the docs for Cookiecutter-Django. The first thing we’ll do is get our project started with a build and migrate. The primary goal will be to illustrate the deployment process. We’ll be getting the site up and running with as little coding as possible for this example. $ git commit -m "initial commit" $ git remote add origin $ git push -u origin master I’ll be posting the repo publicly on my GitHub. This will be where we work prior to deployment.
#AWS POSTGRESQL APACHE DJANGO SOFTWARE LICENSE#
domain_name : version : 0.0.1 timezone : America/Los_Angeles use_whitenoise : y use_celery : n use_mailhog : n use_sentry : n use_pycharm : n windows : n use_docker : y use_heroku : n use_compressor : n Select postgresql_version: 1 - 11.3 2 - 10.8 3 - 9.6 4 - 9.5 5 - 9.4 Choose from 1, 2, 3, 4, 5 : 1 Select js_task_runner: 1 - None 2 - Gulp Choose from 1, 2 : 1 Select cloud_provider: 1 - AWS 2 - GCP 3 - None Choose from 1, 2, 3 : 1 custom_bootstrap_compilation : n Select open_source_license: 1 - MIT 2 - BSD 3 - GPLv3 4 - Apache Software License 2.0 5 - Not open source Choose from 1, 2, 3, 4, 5 : 1 keep_local_envs_in_vcs : y debug: yĬhange directories into the project to view the output of the script.
project_name : cookiecutter_example project_slug : cookiecutter_example author_name : Matthew Wimberly email description : An example project. $ cookiecutter Cloning into 'cookiecutter-django'. This example is adapted slightly from the GitHub page for Cookiecutter-Django. I’ll go over each of my selections below this code block. The answers to the script below will change based on your project’s needs. I’m going to be using a bare-bones example with the configuration below for Cookiecutter-Django and Docker.
0 kommentar(er)
