v2.1 Final release

Nextflight-bt

This will be the last release I'll do for this bot. I learned quite a lot on the process of developing it.

Changes

• Changed Dockerfile, making it more consistent and readable.
• Replaced core image to make the whole image lightweight, using a slim version of Python.
• Changed token read with a basic file reading instead of using sys.env.

And that's all, I hope you find it useful.

v.2.0.1 Small fixes

Small fixes

Makefile and Docker

Added the two commands required to deploy the bot using Docker to the Makefile, making the deployment even easier:

• dockerbuild => Builds the project and creates its image using the Dockerfile => docker build --tag nextflight-bot .
• dockerrun => Runs the bot by running the container detached from the terminal .

Code

A command (nextevent) from the commands message is no longer missing.

v2.0.0 Finished Project

Finished Project

Events

• Added the \nextevent, which gives the user information about the next space related event, like EVAs, dock/undock of capsules on the ISS, press releases/conferences, etc... It also gives a link to the press release (web page) and the streaming link in which the event will take place.

Docker

• Added a Dockerfile to be able to deploy the bot on a Docker container, making it's deployment and management easier.

Fixes

• Fixed some bugs I've detected while testing, like None values, and mistakes I made while implementing or refactoring some pieces of the code to make it more reusable.

And this is the last release of new features of this project since I've done what I wanted, I've learned quite a few of things and I want to move to other projects I want to do.
Future releases will be only of bugs fixes.

See ya and thanks!

v1.4.0 Fixes and minor changes

Fixes and minor changes

Fixed '/cancel' command

I spotted and issue with the /cancel command, which sometimes wasn't recognized and wasn't working properly. It source was that no /cancel command was established on the conversation handler state LOOP, which made that every call to that command was not recognized and was deemed unknown.

Makefile command for the token

To make it easy for the users, I've created a new Makefile command to create the environment variable containing the token (see README.md#Credentials).

Some cleaning

I've done some cleaning of the code, deleting useless code and some pieces I find out redundant. I've added some comments.
Nothing special to be honest.

And that's all for now.
I don't have much time since I'm back on the university, so I'll try to keep up with this project as soon as possible.

Fixes, fixes and more fixes

Fixes, fixes and more fixes

Issue with /cancel fixed

An error concerning the /cancel and not being able to send any other command except this one has been fixed.
This error was caused by a poor "conversation handler" code, which translated on a strange flow of the conversation, leading to errors and bugs, which has been solved bu creating and only using a "conversation handler" with en entry_point, two states, the location request ( LOCATION ) and the execution loop ( LOOP ), and a fallback or "exit point".

This in only a small fix to a annoying error, but a needed fix for future features.
See ya'!

v1.3.0 - Cleaner and less buggy code

Cleaner and less buggy code

Cleaner code

• The code to send the messages has been moved, because having that many times the same code was... quite a pain to the eyes. Now, both methods to send a message (text, and with photo) has been moved to their own file (msg_management.py), leaving the core file more readable and clean.

Fixes

• While deploying the bot, I've found some bugs with the installation process, mainly related to Python and pip installation/presence on the system (having by default Python 2 was the main problem to be honest).
• Also, a package was causing some problems and, after researching a bit, I've found that it was useless, and without it, the installation of dependencies ended without a single problem.

Bugs found

• I'v found a bug with the /cancel command, which locks the conversation and doesn't let the user restart it. I've disabled this command, and once it's fixed, it will be available again.

Some changes, not many, but it's better than nothing 😋
See ya!

Hunting bugs, cleaning a bit and more!

Bugs, doing some cleaning and fixing time zones

Bugs

• There were some bugs related to the proper transformation of UTC dates and times to the user timezone which are now fixed.
• Typos and comments have been fixed.

Some cleaning

• New Makefile to make things easier for everyone (specially for me 😋)
• Added GNU GPL v3.0 to let everyone use this code if they want to, as I said, I'm doing this for me, both because I want a bot like this and because I wanted to carry a project like this.
• New structure of the files, to keep the standard python project structure, even though quite a lot of people differ on how the structure of a python project should look.
• The code of the /nextflight command has been moved to a new file to make the original file more readable.

Fixing time zones

• Fixed the error error on the time zones feature which caused all of the dates and times to stay on UTC, regardless of the user timezone or choice.
• Now, the /skip command will do nothing after the location has been (or nor) given.

And I think that's all... for now, since I add new features and things almost everyday... and whenever they occur to me.

See ya!

Timezones, bugs and command(s)

Timezones, bugs and command(s)

More features have arrived

Although this release doesn't look big enough, there's been some changes to the code, a lot of bugs have been fixed, and many typos too.
There are some new features as well:

• After the start message, the bot ask the user location, used ONLY to find out it's timezone using TimezoneFinder, and only it's timezone is stored.
• Window start, close and NET now follow the timezone given by the user.
• There were many bugs and typos, that are now fixed.
• The text on the messages sent to the user has been moved to a different file

And that's all folks!

Release v1.0

Release v1.0

First release of Nextflight_bot

This first release establish the foundations of this Telegram bot.

The bot is completely functional, offering the user information of the next space flight, like the name of the rocket and the payload, the dates and times (UTC at the moment), mission type and orbit, location and pad of the launch, and if it's available, the infographic of the rocket. If it isn't, it will be a photo of the rocket, and if this isn't possible either, no photo will be attached.