A collection of apps used in allink cms-projects.
allink-core is a heavily opinionated collection of django apps, django-cms plugins and other utilities. allink-core was implemented to create a standardized ecosystem for django-cms projects developed at allink AG.
allink-core is ment to be used with our boilerplate project which is hosted on the divio cloud. (feel free to send us a message if you would like to have a look.) The steps we describe here are mostly closely coupled to our setup and environment. So the described steps might not make sense to you, when you don't know our setup. Also we skip steps which we already included in the boilerplate.
Working on documentation
Workflow when making updates to allink-core repo while working on a project.
The idea is that we want to be able to make changes to the allink-core repo with real life data. This can be achieved, when we are able to switch out the installed allink-core form the requirements.in with a local allink-core repo. This way we can also maintain a proper git history.
Prepare allink-core repository
To work on the allink-core repo you first need to pull the allink-core repo. The setup expects it to be at "~/projects/allink-core". If it isn't in this location, just create a symlink which points to your allink-core repo.
- make sure you are up to date with the current version branch e.g "v2.0.x" and you working on your own branch.
- create a virtualenv
- install requirements
pip install -r requiremnts_dev.txt
For the next steps, we assume you are working on the boilerplate-2.0 project, but this should work with every project which follows the same principles and have allink-core installed.
Prepare boilerplate-2.0 repository
- To override the already installed allink-core requirements, we have to mount the local allink-core directory as a volume into the docker container. Add
- "~/projects/allink-core/allink_core:/app/allink_core:rw"to the docker-compose.yml file.
- To work directly on allink-core in the same directory as the boilerplate-project, we create a symlink.
ln -s ~/projects/allink-core/allink_core allink_core
Make sure you do not commit these changes, as your teammates probably do not care about having a local allink-core mapped in their project.
You are all set. When you now run
docker-compose up your application will run with your local allink-core repo. However if you run
docker-compose build you will still be installing the allink-core repo from the requirements file.
create a new release of allink-core
- create a new pull request (make sure you include your changes to CHANGELOG.md)
- merge back to version branch e.g v2.0.x
make minordepending on what version you want to create. (this will create a new commit and push the new tags to github) If you need an other version do it with
- create a new release on PyPi
make publish(make sure you have the correct credentials for allink in your ~/.pypirc also for test-pypi)
Release history Release notifications
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size allink_core-2.1.0-py3-none-any.whl (569.9 kB)||File type Wheel||Python version py3||Upload date||Hashes View|
|Filename, size allink-core-2.1.0.tar.gz (258.1 kB)||File type Source||Python version None||Upload date||Hashes View|
Hashes for allink_core-2.1.0-py3-none-any.whl