cgallemore / djvasa Goto Github PK

Not liking the current impl, make it better.

Almost positive this is an issue, as I ran into it on another project I'm doing. The issue is that the minon config needs to contain the appropriate mysql settings. Need to verify this.

Create a moth so when uses ssh, they will have a welcome message and some instructions to get them going. Instructions should be based off flags set.

motd:
file.managed:
- name: /etc/motd
- source: salt://motd

app.yaml

Not sure, what else is needed here.

Created a project initialized for Heroku, and it deployed fine to Heroku, or so it seemed. When I went to run the syncdb command I got an error, something about postgres not running. When I tried to go to /admin got the same error.

Add a switch from the command line to set the project up for deployment to Heroku

• Procfile
• database settings

Create the necessary templates needed to setup a postgres database.

• Vagrantfile
• top.sls
• requirements.sls

Whatever else is needed to get Django running.

User already has a django project and all the really want is the vagrant stuff. Should be able to cd into project root and run something like:

djvasa --no-django

And create all the relevant vagrant setup.

The more I think about it, the better I think it would be to instead of using my own template, it would be better to make it configurable to pass in a project template like:

https://github.com/twoscoops/django-twoscoops-project

I know there are others out there as well, like the one from lincoln loop. By default we could just use the twoscoops one out of the box, buy maybe another cli option to pass in a template name of your choice.

Create base Django template.

Been meaning to see what it would take to deploy a Django app to OpenShift. Seems as good a time as any.

Eventually will want to set this up on rtfd, so I need to organize and create some documentation.

1. License file
2. Update long description
3. Go over setup.py and ensure everything is correct.

There should be a global config so the user doesn't have to toggle the same options all the time. For example, I'm thinking a .djvasa file in the users home directory:

[djvasa]
email='[email protected]'
full_name='Chad Gallemore
heroku=True

https://devcenter.heroku.com/articles/django#django-settings

Also, should probably update requirements for heroku option to use django-toolbelt.

To simplify the code, when creating the files, the key should be dvcs and the file name should either be .gitignore or .hgignore.

Add salt script to setup MySQL

Yeah, I know, should have done this first, but whatevs..

Add switch to set up the project for Bootstrap and FontAwesome.