starek4 / fly Goto Github PK

At least on UNIX, the logfile is created in the $PWD when was the run script launched. Maybe we should store it somewhere else? Perhaps in /var/log/fly/ ?

Passwords in database are no longer hashed. Totally forgot about registration form when #1 went live. Oh boy...

Make presentation video of fly application.

Consider using Xamarin.Forms.

Do proper logging class and use it in PHP web api. Log each request in some readable form.

Find other way how to properly test client api implementation.

Created as requested...

Edit webpage API for supporting new actions which will be supported in v2.

• create an icon and use it in every Fly product
• unite design in GUI applications (at least colors and effects)

Do not exit app if there are some problems with the network. Just inform the user by changing the icon or something like that and wait for proper network connection.

Provide manual device deletion from database in web UI.

As title says. API returns NULL when an empty device list is returned from database.

Need to be extra careful while handling exceptions about network connection (connection, timeouts, etc.).

Create GUI for the client where the user can log in and see a list of his devices. After closing or minimizing this app moved it into system tray (same as TeamViewer).

Why we need GUI on Windows but not on Unix based OS's?
Windows users are used to using GUI applications. Just a few windows users know how to run the app from the console and provide right parameters. Linux users are more familiar with CLI and they can provide basic arguments.

Convert actual PHP code to MVC pattern.

Fix logger for globally windows clients...

There is a problem with missing user verification in some web API methods.

I believe we have talked about it, but I can't find it documented here.

We need to store logs in appropriate location, but /var/log is not accessible directly. Thus we need to use syslog. As this will be resolved, the work on #6 can continue.

Provide guides for at least most common distributions. As this will be resolved #13 can be closed too.

This will be a little bit research. We have to find out if we can easily support mute, restart and sleep on all supported platforms.

Edit webpage UI for supporting new actions which will be supported in v2.

Rework returns data types (string which can contain "yes" or "no" -> bool). In client code map returns state to for example ENUM or something like that.

We need to store logged status (maybe in DB?), because now the user has to set his credentials with every start of the client.

Do research how web API should be done in the most right way and implement it like that. It should be done in PHP, because of compatibility with the web app.

Create fallback to ip addr and after fallback on install one of them :)

Edit database schema for supporting new actions which will be added in v2.

Separate API from shared project to a standalone dynamic library (.dll). Make sure to add all NuGet dependencies.

API and all clients should work with the password in a way that after dumping memory it will not be visible.

Do new phone app supporting new actions. Consider MVVM and other good practices.

Running from another folder than the bin/ in project folder tree seems throwing some errors.
First, dotnet requires libhostpolicy.so library to run that client.
Second, when attempting to run (now with the shared library mentioned earlier), the dotnet cannot resolve some CoreCRL path. So far, I tried to copy over the whole bin/ content, but it didn't help at all.

Directly affects #3

Idea from #6
Should be quite easy on Unix, I am not sure about Windows.