Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add procfile for Heroku deployment #7

Open
avhadpooja opened this issue Feb 13, 2018 · 3 comments
Open

Add procfile for Heroku deployment #7

avhadpooja opened this issue Feb 13, 2018 · 3 comments

Comments

@avhadpooja
Copy link

avhadpooja commented Feb 13, 2018

Hi,
Proc file is missing for deployment on Heroku. Can you provide some assistance for the same?

@gingeleski
Copy link
Member

I don't use the Heroku platform but once you first push the app, you'll have to do this in the environment:

  1. Make sure virtualenv is installed (pip install virtualenv I think, Heroku presumably has Python already)
  2. Make sure your pwd is the root of this repo
  3. virtualenv venv
  4. ./venv/scripts/activate.sh
  5. pip install -r requirements.txt

And from then on to start the app it's just a matter of ./venv/scripts/activate.sh then python run.py.

So your procfile (I'm not that familiar with them either) might look like:

web: ./venv/scripts/activate.sh; python run.py

Assuming you don't need fully qualified paths and semi-colons are allowed.

If this works or you figure it out, feel free to open a pull request. 👍

@gingeleski gingeleski changed the title Heroku deployment Add procfile for Heroku deployment Feb 13, 2018
@avhadpooja
Copy link
Author

avhadpooja commented Feb 13, 2018

Thank you for the information on Heroku. I want to integrate this tool into another existing scanner. Is there an API that I can use to extend jawfish?

@gingeleski
Copy link
Member

Not the way it's currently written - I coded this as a younger, more naive developer. At the moment the bulk of its work is client-side (in-browser).

I agree that it would be more useful in such a setup. It could be included in a devops pipeline. The UI could go to Electron from the current browser-based solution.

Opening a separate issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants