-
Notifications
You must be signed in to change notification settings - Fork 84
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
Running on AWS #616
Comments
That code hasn't been touched for a long time and pre-dates me but I believe there used to be some functionality for running on AWS and interacting with Alexa. There have been a few partially completed efforts to make an API and user interface for AIrsenal over the years (and then we could consider hosting it somewhere), but nothing we've had time to finish. |
This is what I was thinking to run this completely headless so it would also execute the transfers etc without any interaction from me. I had it running on AWS and it would send me SNS telling me what transfers to execute but then I tried using the API to automate the subs which was when I got into the issue of the Captcha. So now I just run it on AWS and have it notify me of what transfers to execute via SNS. Thinking of changing it to email notifications as the SNS tend to look messy. |
It wouldn't be too hard, I'll do it in a fork next week. I'm thinking just a systemctl service or a cron job and it just needs to run pipeline and transfers. |
Sorry not really an issue more of a query.
Whats the AWS scripts functionality? Also have you looked at migrating this to AWS services?
The text was updated successfully, but these errors were encountered: