Website: https://www.dcastack.com/

Twitter: https://twitter.com/DcaStack

New github: https://github.com/DCAStack

Website: https://www.dcastack.com/

Full Docs: https://docs.dcastack.com/

Support Us: https://www.dcastack.com/donate

This github repo was made in the spirit of Don't Trust, Verify. I totally understand the hesitation of using web apps created by strangers on the internet. Especially when it comes to sensitive information like API keys and your crypto. So to help foster trust and gather early user feedback, I'm releasing the source code that directly builds the production environment.

This is a super early preview of DCA Stack. What this means for you, the user, is that there are bugs! What I'm hoping is that with community testing that we can squash these bugs and create a super robust DCA service. Keeping in mind that this is just an alpha release, please only keep funds necessary to faciliate order trading. This will mitigate the risk of using this early release of DCA stack.

If you find any bugs, please feel free to open an issue and include as much detail as possible!

Excellent question and totally valid concern. We can verify this directly from github! You must be signed in on github btw.

Simple answer: On the right hand side of the screen (or left), there will be a section called Environments. Click on it. You'll see a button called View Deployment. Click on that and that'll take you to the website that this repo builds. The exact code you see on the repo is what is contained in the deployment since it is an automated process.

Better answer: The way this repo is configured is that whenever the main branch receives a new commit, it will trigger an automated workflow. This workflow will rebuild the repo and automatically deploy the code to the server. So the code you see in the repo is the exact same code that is being served by the server since it is a complete automated process Github offers it's users (along with heroku).

You will notice that this takes you to dcastack.herokuapp.com which is the direct connection to the heroku platform on which this entire website is hosted. This is the exact same as the dcastack.com domain. The only difference is the fact that dcastack.com is more convenient for SEO, spreading the word and enhanced with cloudflare.

First, download Docker here: https://www.docker.com/products/docker-desktop

Second, let's see if we can get this webapp going. Open up a terminal, clone this repo and enter the folder. We are going to make a .env file in the current location you are in. Here is what that looks like:

SECRET_KEY=YouShouldRandomlyGenerateThis
MAIL_SERVER=YourMailServer
MAIL_PORT=YourPort
MAIL_USE_TLS=TrueorFalse
MAIL_USE_SSL=TrueorFalse
MAIL_USERNAME=YourMailUsername
MAIL_PASSWORD=YourMailPassword
REDIS_URL=redis://redis-server:6379/0
SET_SANDBOX=False
SET_DEBUG=False
SENTRY_FLASK_KEY=Sign up here: https://sentry.io/ and get a client key (DSN) for flask project
SENTRY_CELERY_KEY=Sign up here: https://sentry.io/ and get a client key (DSN) for celery project

Third, we need a .flaskenv file, add this:

FLASK_APP=project
FLASK_ENV=development
FLASK_DEBUG=1

Fourth, let's do the following outside the REPO directory. This will generate the sqlite DB for working locally.

python3 -m venv YOUR_ENV_NAME_HERE
source YOUR_ENV_NAME_HERE/bin/activate
cd REPO_NAME
pip install -r requirements.txt
python3 manage.py db init

Finally, let's get docker up!

docker-compose up -d --build

And that's it. Open your browser to http://localhost:5000 to view the app or to http://localhost:5556 to view the Flower dashboard (this is for viewing celery tasks running).