Once you do you'll see a list of possible changes you can add. You should have been saving your code using file.save while you've been working, but if you haven't go ahead and do that. Since this is on Gitpod, it's automatically connected to your remote repository. So let's use Gitpod's source control tab to push our to the remote repository (GitLab). Like I said before, git is important, and that repository you created earlier on GitLab needs all the files you've been making in Gitpod. This is a continuation of a series on Twitter bots! In the previous article, we made a bot that tweets Super Nintendo soundtracks every week! In this article, we're going to learn how to host it using Heroku! But first, let's talk about what to do with your repository. Keep your web dyno alive by pinging it at least once every 30 minutes.though that might not make a lot of sense for your application Move your free worker dyno to another app that has no web dynos to prevent it from sleeping.maybe run it once an hour for a limited amount of time / tweets Run your worker regularly (but not constantly) via the Heroku Scheduler.In addition to the web dyno sleeping, the worker dyno (if present) will also sleep.įree worker dynos on apps that do not have a web dyno do not sleep, but of course they'll consume roughly 720 free dyno hours every month (24 hours per day × 30 days in the month). If an app has a free web dyno, and that dyno receives no web traffic in a 30-minute period, it will sleep. Your Procfile shows that you have a web process and a worker process.Īssuming you are using free dynos, this behaviour is expected (bold added):

Secret = environ #Access token secretĪuth = tweepy.OAuthHandler(consumer_key, consumer_secret) # AuthenticationĪuth.set_access_token(key, secret) # Grant access to API I don't know if it's the dyno or something else.Ĭonsumer_key = environ #API keyĬonsumer_secret = environ #API key scret I'm quite new to the Heroku platform, I don't understand why my Twitter bot deployed gets shut down after some time.

Dyno bot twitter