offen/website
2
0
Fork 0
mirror of https://github.com/offen/website.git synced 2024-12-23 13:30:20 +01:00
Code Issues Projects Releases Wiki Activity
Mirror of github.com/offen/website
274 Commits 2 Branches 0 Tags 32 MiB
HTML 63.2%
CSS 20%
Python 10.9%
Makefile 4.4%
JavaScript 0.8%
Other 0.7%
b0dc098c43
Go to file
Frederik Ring b0dc098c43 Merge pull request #115 from offen/pip-install 
Add missing install step to setup target
2019-09-21 11:26:29 +02:00
.circleci do not use bashenv in alpine based image 2019-09-14 14:55:04 +02:00
.elasticbeanstalk introduce staging environment 2019-09-14 14:35:04 +02:00
build/proxy remove bad reference to deleted directory 2019-09-13 12:54:02 +02:00
homepage update homepage wording 2019-09-19 14:20:52 +02:00
.ebignore leverage layer caching for node deps 2019-09-09 22:30:11 +02:00
.editorconfig add logspout container to production setup 2019-09-16 15:53:16 +02:00
.gitignore consider lockfiles when building docker images 2019-09-11 21:39:16 +02:00
CODE_OF_CONDUCT.md refer to real world .dev domain 2019-05-01 20:34:00 -06:00
docker-compose.yml default to secure cookies 2019-09-11 20:31:45 +02:00
Dockerfile.python scaffold accounts app 2019-07-05 20:37:39 +02:00
Dockerrun.aws.json.production add logspout container to production setup 2019-09-16 15:53:16 +02:00
Dockerrun.aws.json.staging introduce staging environment 2019-09-14 14:35:04 +02:00
LICENSE Initial commit 2019-04-10 16:58:26 +02:00
Makefile add missing install step to setup target 2019-09-21 11:19:22 +02:00
README.md configure production environment 2019-09-11 12:55:17 +02:00

README.md

offen

CircleCI Pivotal Tracker Patreon

The offen analytics software

This repository contains all source code needed to build and run offen, both on the server as well as on the client. See each of the READMEs in the subdirectories for instructions on how to work on that particular area of the application.

Development of offen has just started, so instructions are rare and things will stay highly volatile for quite some while.

Guidelines for running and developing the Software will be added when it makes sense to do so.

Project planning and issue tracking is done using Pivotal Tracker, but feel free to open a GitHub issue if you have a question or found a bug.

Developing the application

The development setup requires docker and docker-compose to be installed.

After cloning the repository, you can build the containers and install dependencies using:

$ make setup

Next, create a local encryption key for the kms service and seed the database for the server application:

$ make bootstrap

You can test your setup by starting the application:

$ docker-compose up

which should enable you to access http://localhost:8080/auditorium/ and use the auditorium

License

MIT © offen