DISCONTINUED

bitlabstudio, updated 🕥 2022-01-21 18:57:23

Important

This app has been discontinued and is no longer maintained.

Webfaction Django 1.4 Boilerplate

Use it, if you know what you are doing

This boilerplate has been tested with a fresh Webfaction server with Django 1.4 on May 24 2012. It worked without any issues. However, if you use it and fab install_everything crashes you will have read the fabric error message carefully, think hard about what might have gone wrong, probably fix the fabfile (and open an issue here) and try again. The fab task is setup in such a way that it deletes previous failed attempts on the server so that it can be run over and over again.

This project will help you to start new Django projects on Webfaction servers.

Naming conventions

Throughout the instructions we will stick to the following naming conventions:

username is your webfaction username. You will want to chose a username as short as possible since database names have to start with username_ and are quite limited in length.
yourproject is the name of your project. You will probably name your folder on your local development environment like this. It should be a short name as well.
We will prepend or append yourproject at many places. We could just name your apps django, static and media etc. but we want to make sure that you are able to host several projects on one machine in a clean and manageable way. Most likely yourproject and username will be the same for your first site.
yourdomain.com is the domain that you want to use.

Webfaction panel

Before you can start to deploy your Django site on your Webfaction server, you need to add various settings at your Webfaction control panel:

First, change your control panel password
Next, change your SSH/FTP password
Go to domains management
Add the domain git.username.webfactional.com
Add the domain yourdomain.com and www.yourdomain.com
Go to applications management
Create a new Django app Django X.X.X (mod_wsgi 3.3/Python 2.7). Call it
yourproject_django. Just select the latest release. It doesn't really matter because we will use a virtualenv anyways.
Create a new Static app Static only (no .htaccess). Call it yourproject_media and enable expires max.
Create a new Static app Static only (no .htaccess). Call it yourproject_static and enable expires max.
Create a new app Static/CGI/PHP-5.3. Call it yourproject_www.
Create a new app Git. Call it git and enter a password.
Go to website management
Add a new site called yourproject and map yourproject_django to /, yourproject_media to /media and yourproject_static to /static.
Use the subdomains username.webfactional.com, yourdomain.com and www.yourdomain.com.
Add a new site called git and map git to /.
Mark it as HTTPS
Use the subdomain git.username.webfactional.com
Go to database management
Create your database (username_yourproject) and note down the password. You should create a PostgreSQL database as the latest MySQL has problems with south migrations of easy_thumbnails.
Got to email management
Crate a new mailbox (username_yourproject) and note down the password.

Local machine

First setup your local virtualenv. If you are not familiar with virtualenv and virtualenvwrapper we strongly recommend to have a look at those first:

mkvirtualenv -p python2.7 yourproject
workon yourproject

Next cd into your desired project folder and clone this repository:

cd $HOME/Projects
mkdir yourproject
cd yourproject
git clone git://github.com/bitmazk/webfaction-django1.4-boilerplate.git src

Now you can install the requirements for the project:

cd src
workon yourproject
pip install -r website/webapps/django/myproject/requirements.txt --upgrade

Next you need to copy fabric_settings.py.sample and modify it for your needs. Basically you just need to modify your webfaction username and your desired project name. Usually both will be the same unless you are hosting several Django apps on the same Webfaction server. It also holds some values that will be inserted into your server's local_settings.py.

cp fabric_settings.py.sample fabric_settings.py

You need to create a .ssh directory on your Webfaction server with permissions setup properly. Once you have done that, copy your public rsa key into your clipboard, ssh into your Webfaction server and append your key to .ssh/authorized_keys. If you have already done sone, you can skip this step. It will setup the .ssh folder on your server according to the Webfaction user guide on accessing your data using SSH keys:

fab run_create_ssh_dir

You can check if everything worked by exiting your ssh session and creating a new one immediately after. This time you should not be asked for a password any more.

Since you are on the server now anyways, you might consider to install our Webfaction dotfiles.

From now on we will use a fabric file that will setup your local repository and deploy it on your webfaction server. First it will prepare your local repository. Obviously you cloned this boilerplate repository but you don't want our history in your new project's history. So first the fabfile delete the .git folder and .gitmodules, run git init, add submodules, copy local settings files and run syncdb and loaddata.

After this you should be able to cd into the project folder, run ./manage.py runserver and login to /admin-XXXX/ with username admin and password test123.

Next it will login to your Webfaction server and create a git repository, hook up your local repo with the one on the server and do a push. It will install many useful scripts for django-cleanup, database backups, media-files backups and translation catalogues backups. It will install cronjobs, place a .pgpass file, install virtualenv and virtualenvwrapper, make changes to the .bashrc file, clone your repo into the folder /src, install the requirements.txt and do a first deployment, which will run syncdb, migrate, collectstatic and makemessages. And for all this goodness you only need one command:

# The task will only halt once and ask for your git password
fab install_everything

This will run for up to 20 minutes or so. Afterwards you will have a ready to go local project that is also deployed on your Webfaction server.

We even went one step further and provided initial fixtures which should give you everything you need for a normal website. In order to install the fixtures locally do the following. If you just want to create your own CMS pages and start creating your templates, you can skp this step:

cd website/webapps/django/project
fab rebuild
./manage.py runserver

The idea behind this rebuild command is that a new developer should never be forced to download the lates database from production in order to get started. Instead we should always provide fixtures that setup enough test data so that a new developer can run fab rebuild and as a result he will see a fresh database that has all needed CMS pages and apphooks and lorem ipsum blog posts and other test data inside.

Your development workflows might differ, so you can just ignore this command.

Webfaction server

At this point you are able to browse to username.webfactional.com and see the django-cms welcome screen. First you should login at /admin-XXXX/ with username admin and password test123 and change your password.

The next thing you should do is ssh into your Webfaction server and change the secret key in $HOME/webapps/yourproject_django/myproject/settings/local/local_settings.py.

You should also change the ADMIN_URL setting in your local_settings.py and set it to a random number.

If you want to make use of the fab rebuild command on your server as well, you should run:

workon yourproject
pip install fabric
pip install coverage
cd $HOME/webapps/yourproject_django/myproject/
fab rebuild

This setup assumes that you are deploying a multilingual project, so you would want to create your first translation catalogues now:

cd $HOME/webapps/yourproject_django/myproject/
workon yourproject
./manage.py makemessages -l ch_ZN

If you don't intend to use i18n, you can remove the scheduled backups from crontab:

crontab -e
# remove the line about locale-backup.sh

Misc

In your local project you should change the recepients for the contact form app. Usually this should be your customers [email protected] address. You can find the file at ../myproject/settings/installed_apps/contact_form.py.

You should also have a look at ../myproject/templates/base.html and change the site name that gets appended to the title. If you are using Google Analytics, you should enter your ID, if not, you should delete the analytics code snippet.

TODO

it seems as if the script deletes existing .pgpass file on the server?
Document what gets changed and how to revert in case of failure
fab rebuild does not work because there is no test_media
Why is there a fabfile_settings.py-r and urls.py-r after install everything?
Add delete_project task
Only add cronjobs if not there already
Make sure django forwards to www
Autogenerate secret key
Use ssh for git authentication

Issues

Bump ipython from 0.13 to 7.16.3 in /website/webapps/django/myproject

opened on 2022-01-21 18:57:22 by dependabot[bot]

Bumps ipython from 0.13 to 7.16.3.

Release notes

Sourced from ipython's releases.

7.9.0

No release notes provided.

7.8.0

No release notes provided.

7.7.0

No release notes provided.

7.6.1

No release notes provided.

7.6.0

No release notes provided.

7.5.0

No release notes provided.

7.4.0

No release notes provided.

7.3.0

No release notes provided.

7.2.0

No release notes provided.

7.1.1

No release notes provided.

7.1.0

No release notes provided.

7.0.1

No release notes provided.

7.0.0

No release notes provided.

7.0.0-doc

No release notes provided.

7.0.0rc1

No release notes provided.

7.0.0b1

No release notes provided.

6.2.1

No release notes provided.

... (truncated)

Commits

d43c7c7 release 7.16.3
5fa1e40 Merge pull request from GHSA-pq7m-3gw7-gq5x
8df8971 back to dev
9f477b7 release 7.16.2
138f266 bring back release helper from master branch
5aa3634 Merge pull request #13341 from meeseeksmachine/auto-backport-of-pr-13335-on-7...
bcae8e0 Backport PR #13335: What's new 7.16.2
8fcdcd3 Pin Jedi to <0.17.2.
2486838 release 7.16.1
20bdc6f fix conda build
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/bitlabstudio/webfaction-django1.4-boilerplate/network/alerts).

Bump django from 1.4.1 to 2.2.24 in /website/webapps/django/myproject

opened on 2021-06-10 17:40:31 by dependabot[bot]

Bumps django from 1.4.1 to 2.2.24.

Commits

2da029d [2.2.x] Bumped version for 2.2.24 release.
f27c38a [2.2.x] Fixed CVE-2021-33571 -- Prevented leading zeros in IPv4 addresses.
053cc95 [2.2.x] Fixed CVE-2021-33203 -- Fixed potential path-traversal via admindocs'...
6229d87 [2.2.x] Confirmed release date for Django 2.2.24.
f163ad5 [2.2.x] Added stub release notes and date for Django 2.2.24.
bed1755 [2.2.x] Changed IRC references to Libera.Chat.
63f0d7a [2.2.x] Refs #32718 -- Fixed file_storage.test_generate_filename and model_fi...
5fe4970 [2.2.x] Post-release version bump.
61f814f [2.2.x] Bumped version for 2.2.23 release.
b8ecb06 [2.2.x] Fixed #32718 -- Relaxed file name validation in FileField.
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

add django-send-mail script

opened on 2012-07-25 05:00:56 by mbrochh

Since we are using django-mailer we should add a script for sending mail and add it to the crontab as well

Bitlab Studio

Custom crafted Android, iOS and Web-Apps for Businesses and Startups

GitHub Repository

*DISCONTINUED*

Important

Webfaction Django 1.4 Boilerplate

Use it, if you know what you are doing

Naming conventions

Webfaction panel

Local machine

Webfaction server

Misc

TODO

Issues

Bump ipython from 0.13 to 7.16.3 in /website/webapps/django/myproject

7.9.0

7.8.0

7.7.0

7.6.1

7.6.0

7.5.0

7.4.0

7.3.0

7.2.0

7.1.1

7.1.0

7.0.1

7.0.0

7.0.0-doc

7.0.0rc1

7.0.0b1

6.2.1

Bump django from 1.4.1 to 2.2.24 in /website/webapps/django/myproject

add django-send-mail script

Bitlab Studio

DISCONTINUED